Where is the DACs documentation? I can’t find anything about BAccount, BAccount2, etc.
In the same DAC extension, can I reference a different field in the selector query? For example, the user selects a customer and then I want to populate another field with that customer’s projects.
Is it best practice to put each customization in its own “project”, i.e. I have a customization the SO screen and another for the PO screen.
Should all customizations for the same screen be in the same “project”?
Page 1 / 1
Hi @robtrainer6184
First, Welcome to Acumatica and the Community
I am not a developer but there are a few things here that I can assist you with.
& 4. Customizations can be combined, although you will need to be careful of what will work together and ensure code does not affect other areas if they are not related (aka stepping on each other). I’ve seen many developers do it both ways, combining projects for different screens and also making them separate.
Good Luck also!
@robtrainer6184 - Please use help.acumatica.com for all of these questions.
@StevenRatner I have done that. There is no reference to BAccount2 or BAccountR in help.acumatica.com.
@StevenRatner I have done that. There is no reference to BAccount2 or BAccountR in help.acumatica.com.
I’m not sure why my answer didn’t post earlier, but have you looked directly at the DAC?
I have seen BAccount2 in the schema browser but that does not document what it is relative to BAccount nor does it tell you any information about why it should be used instead of BAccount.
Basically, I don’t consider it documentation.
Hi @robtrainer6184
Have you looked on Stack Overflow? I know there is a great deal of information there.
IN this post, it states that BAccount2 and BAccountR are subclasses of BAccount. (This is an older post though)
Yes, I have seen numerous references to BAccount2 and BAccountR on stackoverflow and here on this forum. But nowhere have I seen why I should use it versus BAccount.
From what I understand it has to do with the order in which you access the underlying BAccount records, DAC inheritance and caches.
Because the BAccount table contains Customers, Vendors, Employees, etc. the first time you reference BAccount in your graph, all other calls to BAccount will make use of the same cache. So if your first reference to BAccount is to look at customers, then when your subsequent calls to BAccount will be looking at customers.
If you need to look at Vendors or Employees in the same graph, you need to reference BAccount2 or BAccountR. It points to the same table but it allows the cache to differentiate between the two (or three) types of BAccount records.
I Goggled “acumatica baccount baccount2” and the first link describes it in a more technical fashion. (However, at this moment, the blog seems to be down.)
