Questions Custom Report Numbering Best Practices

We usually do something like XX.YY.ZZ.## where:

• XX is a code for our company that doesn't match one of their modules.
• YY is their module code (SO, PO, IN, etc)
• ZZ is a code for what it is.  These are arbitrary, but we have codes for GIs, Reports, Dashboards, etc.
• ## is just an incrementing number to keep things unique.

So for example, if our company code was DI, and our code for report was RP, and we were putting this in the SO module, I'd use something like:  DI.SO.RP.01

Really, it's all arbitrary to just keep the screen IDs unique, but this seemed a good fit for our company.  If Acumatica has a recommended guidelines though, I'd be interested in seeing as well.

Thanks for the prompt response Wyatt.

I have asked Acumatica if they have documented best practices on the subject and I will post their response to this article.

The response from Acumatica was not encouraging.

Basically they do not have an established standard and suggested to look up the forms, generic enquiries and report Id's in the Sales Demo data set to see what is being used by Acumatica; suggesting if we use Id's that are not in the Sales Demo set we should be OK.

Acumatica has some info on this here:

Acumatica Framework Guide - Form and Report Numbering