The Importance of Screen IDs

Acumatica gives every screen a unique ID. This might not seem like a big deal, but I think it is.

In order to see the screen ID, just put your mouse over the name of the screen and the ID will appear (GL633500 in the example below):

or you can see the screen ID in the URL path in the address field of your web browser:

No matter how you determine the screen ID, the important point is that there is a screen ID. This might not seem that important, but it sure helps a lot when you need to refer to a specific screen. For example, the Accounts Payable and Accounts Receivable modules both have a screen with the name Recurring Transactions.

When you are referring to one of the screens in an email, it might be helpful to include the correct screen ID (the one for Accounts Payable or Accounts Receivable). Or, better yet, you could just include a link to the correct screen (replace localhost and AcumaticaERP with your paths of course):
http://localhost/AcumaticaERP/(W(1))/?ScreenId=AP203500. When a user finds the screen by entering the screen ID, they can also see the path to the screen because the navigation page adjusts to show which module and which area of the module the screen is in.

Again, this might not seem like a big deal, but I think that it helps a lot when writing documentation or communicating with colleagues about Acumatica. I often hear people get lazy when talking about screens in an ERP system and the name they use is not the actual screen name, but some creative variant. Having screen IDs helps to set the record straight and prevent misunderstanding, especially among new employees who might spend hours looking for a screen name that doesn’t exist before asking someone for help.

SAP employs the same technique for giving screens an ID (eg. FD01 or XD03). I’m glad that Acumatica does too.