Ideas for Acumatica

Important! Please note that we do not reply to all messages, but we do read them, analyze them, and work to improve Acumatica based on the feedback we receive.
This portal is for product ideas and feedback only. If you need customer service assistance, please contact your Acumatica Support Partner or submit a support case.  You can also get assistance from community resources:  LinkedIn Group or StackOverflow
No Reliance: Information is maintained on a best-efforts basis and may be changed without notice. Acumatica cannot guarantee the accuracy of the information provided or guarantee completion of features/ideas described on this portal. 

Create a DAC Schema Browser

Every major ERP software product has a schema browser. Acumatica should have one too (for the Data Access Classes).

  • Tim Rodman
  • Jul 1 2015
  • Gathering Feedback
  • Attach files
  • Shawn Slavin commented
    November 20, 2015 23:16

    Please.  Would make my life easier.

  • Michael Pratt commented
    November 24, 2015 19:43

    This is essential for businesses, especially for people building inquiries that do not have access to the database. 

  • Guest commented
    February 12, 2016 11:36

    Needed, especially as you can't go to SQL for the information. It's bad enough as developers having to work it out (and cope with unannounced changes) but for "power users" who want to do good things with Generic Inquiry it's a real frustration.

  • Jeremy Potoka commented
    July 16, 2016 17:12

    I agree.  We have so many reasons not to go to SQL since Acumatica is a robust ERP.  This would support the ease of use for everyone and provide solid documentation for building inquiries.

  • David Eichner commented
    July 18, 2016 20:54

    please, please please add this functionality

  • Alex Race commented
    November 04, 2016 18:55

    I have only recently began working with Acumatica and noticed this gap immediately.

  • Valerie Arguin commented
    January 03, 2017 18:26

    Please add this functionality.

  • Brian Rowerdink commented
    February 09, 2017 15:55

    Since I no longer have access to SQL because of the SaaS model a schema would go a long way in helping me create the generic inquiries I need to provide data to my users. Please make this happen. 

  • Tim Rodman commented
    April 18, 2017 21:40

    Since creating a schema would probably be a lot of work, what about this idea? The biggest challenge is identifying what the primary keys are on a Data Access Class (DAC). Once you identify those, doing the join is pretty easy.

    There is a Data Access tab on the Source Code (SM204570) screen in Acumatica that allows you to browse the DACs (and the fields within each DAC). The problem right now is that you have to click on every single field individually and check their properties to know if they are a primary key field or not. If there could be a Primary Keys section on the top of the screen, that would be a HUGE time saver and an acceptable substitute for a schema in my opinion.

  • Shawn Edwards commented
    June 29, 2017 19:32

    I would do some dark, dirty things for this!

  • Joni Girardi commented
    July 18, 2017 15:53

    I've been working with enterprise-grade BI for SMBs for 17 years. While I find the Generic Inquiry very valuable for reporting, I consider the lack of Acumatica database metadata a major limitation for BI best practices. 

  • Robert Lightner commented
    August 10, 2017 20:02

    Well Dahhhhhhhh

  • Jon DeCristofaro commented
    September 26, 2017 16:39

    This is absolutely required. I am freshly shocked every time someone confirms it truly does not exist. (Actually, it MUST exist for internal users, it's just a matter of letting customers have it.)

  • Christine Reeders commented
    January 08, 2018 19:25

    This is one of the largest complaints I'm receiving from clients.

  • Jean McClelland commented
    February 15, 2018 02:52

    Yes, Please!

  • John Lipp commented
    February 22, 2018 22:22

    Would be useful

  • Karen O'Lane commented
    March 06, 2018 03:46

    This is an essential and invaluable tool for business partners. Please make it happen!

  • Brian Kelly commented
    March 06, 2018 13:11

    This must exist already, right?  Perhaps it is simply a matter of putting into an acceptable format for public consumption?  This would be a big win if you could make it part of the user documentation within Acumatica.  Pretty Please with some Stoli on top!!!!  ;-)

  • Cooper Black commented
    March 06, 2018 13:13

    This won't win you any deals but it makes life a lot easier for the partners that work with Acumatica customers.

  • russ williams commented
    April 19, 2018 14:39

    2nd most popular idea on this site and not a word from Acumatica in 3 years.......

  • Meysam Rouhnavaz commented
    May 25, 2018 18:18

    Please add this important functionality for developers

  • Vladimir Panchenko commented
    June 04, 2018 07:53

    Sorry for the late answer.

    Thank you for your suggestion. We'll think about implementing it in the future.

  • Guest commented
    June 04, 2018 10:52

    This is critical - please publish - even if for partners only.

  • Vladimir Panchenko commented
    June 07, 2018 12:39

    I'd like to gather some feedback on the topic.

    Right now we're thinking about the format described below. Feel free to leave any comments.


    Schema Browser will contain a list of DACs grouped by namespace or module (GL, AP, AR, SO, etc.).

    Information about a DAC will be displayed in the following format (let's take PX.Objects.GL.Account as an example):


    Account DAC

    Represents an account of General Ledger. The records of this type are edited through the Chart Of Accounts (GL.20.25.00) screen (corresponds to the AccountMaint graph).


    Is Key Name Description Data Type Display Name Is Required Linked Entity
    x AccountCD User-friendly unique identifier of the account.   string Account x  
      AccountID Unique identifier of the account. Database identity.  int      
    ... ... ... ... ... ... ...
      CuryID Identifier of the PX.Objects.CM.Currency of the account. string Currency   PX.Object.CM.Currency


    When you click on a field's name, details page is shown:


    AccountCD Field

    Key field. The user-friendly unique identifier of the account.






    Is Unicode


    Max Length


    Input Mask




    Segmented Key



    And another example with CuryID field:

    CuryID field

    Identifier of the PX.Objects.CM.Currency of the account.




    Is Unicode


    Max Length


    Linked Entity

    PX.Object.CM.Currency, BQL query: Currency.curyID

  • Jeff Waldron commented
    June 07, 2018 12:45

    Please do NOT do this one for Partners only!  Just release to the customers to save us hours of frustration.  I've never worked on an ERP that didn't have this documented for customers.  I like the format you've proposed.  The last ERP I worked with had two different documents that helped.  The first was a Data Dictionary of all tables in the Database.  The second was a Relationship reference, showing all of the links between the tables.  It was pretty easy to follow.

  • Jean McClelland commented
    June 07, 2018 13:00

    It would be ideal to have a “Where Used” column either in the matrix or the detail. (Probably in the detail because some of them are very long.)

    Jean McClelland, Application Specialist
    Clients First Business Solutions
    Cell: 903.752.2072

  • Guest commented
    June 07, 2018 13:01

    Please add reference to actual SQL Database Table.Field if any.

    Best Regards,
    Alexandre Petrov || Business Analyst, ERP Architect || G&A Ops || Parallels || Office: +7 495 7832977 ext. 70114

  • Rick Van Doel commented
    June 07, 2018 13:07

    Agreed. Developing GIs without understanding the key fields is time consuming and inefficient. 

  • Guest commented
    June 07, 2018 13:35

    How would embedded apps be able to add their data? I add some info to our help for those who need to write queries or reports.  There are areas where more details are required such as business accounts, addresses, contacts, locations, customers, vendors where you have to know how to join the related records.

  • Viktor Zelenko commented
    June 07, 2018 13:46

    Brilliant idea!  This is a standard portion of "Help" files for majority of ERP systems.  See attached examples from SAGE.

    Thank you.

  • Viktor Zelenko commented
    June 07, 2018 13:54

    Hi Vladimir,

    What you suggest below looks good for starters. It will take some time to evolve into full blown help library. Please, see attached examples from SAGE erp help files. This might give you more ideas.

    Thank you,

    Viktor Zelenko
    Software Consultant
    AppSolute Consulting Group
    2 West 45 Street
    Suite 1206
    New York, NY 10036
    Voice: (212) 265-2062 Ext. 206
    Fax: (212) 265-2068

  • Guillermo Pineda commented
    June 07, 2018 14:08

    The DAC schema browser with primary key identification is a must. We get complaints for the lack of it from almost all of our customers.

  • Mike Aichinger commented
    June 07, 2018 14:11

    This is a great start. However, there needs to be definitely the relations piece for instance, when looking at Customers and Vendors the links between the BAccount, Customer/Vendor, Location, Address, etc to build that complete picture, if possible.


    Michael J Aichinger
    Project Manager
    Crestwood Associates LLC
    240 East Lincoln Street
    Mount Prospect IL 60056
    Direct: 847-232-8211
    Mobile: 630-235-7583

    Awarded Acumatica MVP for 2016 & 2017



    Microsoft, Acumatica, and Greentree Gold Certified Partner

    Microsoft Inner Circle Member (2017/2018)
    2-time Acumatica Partner of the Year Award (2016 & 2017)
    2017 Acumatica Cloud Adoption Award
    2017 Acumatica Partner Marketing Evangelist Award
    10-time Microsoft President's Club Award Winner (2016)

    Have a support issue? Please contact our Support Team.

  • Michael Hansen commented
    June 07, 2018 14:28

    I would like to add in to the idea of having a "where it is used" segment for this. With that in hand, even a novice user can start tracing out a path to the table(s) they need, assuming you have live links to click through for each table etc. Some of the key-pairs are not obvious, so it'd be great to have a "visual" representation of the connections even if only through hyperlinks. I am loving this idea more and more every day.

    Also as noted by others, please ensure this gets released to EVERYONE. I have no want to pay my reseller every time I want to know how to quickly link a few objects. The more open and easy to use this ERP is, the more it stands above the competition.

  • Vladimir Panchenko commented
    June 07, 2018 15:11

    It seems that the last column of the table ("Linked Entity") is not shown for some reason. Original idea was to show relations right there like it is with CuryID field (relation with PX.Objects.CM.Currency).

    Jean, what should this column show? A list of forms where this field is used?

    Alexandre, could you please share some use cases when you need SQL field name?

    Yes, we thought about the ability to extend Schema Reference with information related to customizations. We'll try to make that possible.

    Viktor, thank you for the examples. One of the ideas that we can take from it is to also show a DAC Display Name (e.g. "Business Account" for PX.Objects.CR.BAccount).

    Mike, yes, basic relations will be described (inheritance, links to other entities like BAccount -> Address, etc.)

    Michael, one of our recommendations for novice users is to use "Inspect Element" functionality located under Customization menu. It is often easier to start from a data entry screen and find out which DACs are used, and after that use them in the reporting tools. Starting from 2018R1, almost every data entry screen in the system has a corresponding Generic Inquiry configured as an entry point, so you can take a look on it and get some ideas on which DACs to use and how to join them.

  • Tim Rodman commented
    June 07, 2018 15:43

    Vladimir, I like how you included an Is Key field in your mockup. To me that's very important.

    I agree with everyone else that the foreign key relationships are another very important part of this. I'm not sure if it would be better to display them as a comma delimited list in a separate column on the main table or have a hyperlink for each column that you would click on to see them as a list of rows.

    Also, it seems like you already have a starting point with these two hidden screens in the Site Map (screenshots taken from build 18.103.0022):


    Browsing to one of those screens using the Screen ID in the URL, it has a foreign key concept built into it:

  • Paul commented
    June 07, 2018 16:54

    Also, if the field presents a selection list please identify the available selections (i.e. the Sales Order Type field)

  • Jean McClelland commented
    June 07, 2018 18:06

    Yes – a list of forms would be great! Form #s and names.

    Jean McClelland, Application Specialist
    Clients First Business Solutions
    Cell: 903.752.2072

  • Rick Taylor commented
    August 11, 2018 14:37

    It would simplify things to have this.

  • John commented
    September 26, 2018 21:22

    This is badly needed

  • Yuriy Zaletskyy commented
    October 19, 2018 20:25

    I just want to say that currently I developed customization that shows tables in Acumatica. Other features implementation are on it's way. Please write me a message on zaljru1989(a_t) those, who would like be in the group of first users/testers of that feature.

  • Yuriy Zaletskyy commented
    October 23, 2018 09:51

    I provided wrong email in previous post:

  • Yuriy Zaletskyy commented
    October 26, 2018 09:42

    Hi all.

    I have implemented first version of DAC Schema Browser. You can see how it looks in attachments.

    If somebody wants to participate in testing please drop me a line: zaljur1989(animal) or at linkedin:

  • Arline Welty commented
    January 15, 2019 15:17

    Please- this is essential.

  • Alisann Crough commented
    January 22, 2019 19:08

    definitely need this

  • Adam Ferguson commented
    January 31, 2019 05:59

    This should not just be for partners. There are a lot of customers with IT departments as well that would benefit greatly from this. I would assume this would reduce Acumatica support tickets as well - I know I've opened a few requesting guidance on this.

  • Donald Drump commented
    February 28, 2019 16:42

    4 Years later and still nothing. Great job Acumatica

  • Tim Rodman commented
    March 08, 2019 19:53

    This looks to me like a great step in the direction of having a schema. Quite colorful too:

    Here is the video:

    And here is a screenshot from the video:

  • Yuriy Zaletskyy commented
    May 19, 2019 19:06

    I have great news for all, I've decided to open source my implementation of DAC schema browser. You can see how it works here:

    and you can get a source code here:

  • Dominic Albrecht commented
    August 14, 2019 11:34

    @Tim Rodman


    The video you shared on 8 March looks really interesting - do you have any more info on this and when we could use it ?

  • Nut Y commented
    September 05, 2019 09:43

    even nicer if you can select any data field in the form to see origin of information. 

  • Bronwyn Duprey commented
    September 18, 2019 20:36

    Absolutely!!!!  Would make reports & GI so much easier.

  • Tim Rodman commented
    September 28, 2019 21:32

    I just noticed this new thing in Acumatica 2019 R2!

    It's still missing Primary Keys, but it's a start.

    You don't actually need a 2019 R2 environment because the help is available outside of Acumatica: