Skip to main content
Question

How to use 3 character Customization Project initials

  • Nov 3, 2026 7:00 PM UTC
  • 3 replies
  • 21 views
  • Translate All

Forum|alt.badge.img

We are working on a Customization Project and have been assigned the initials DSG for the project.

The Screen Editor only allows two characters to be entered but our validation fails with the following.

Can you please advise how we can address this?

 

New site map screen names must start with the assigned prefix.

SiteMapNode | Billing Accounts | DS131000

Custom screens and reports must start with the assigned prefix.: Billing Accounts ScreenID: DS131000

 

SiteMapNode | Configurations | DS111000

Custom screens and reports must start with the assigned prefix.: Configurations ScreenID: DS111000

 

SiteMapNode | Custom Data | DS121000

Custom screens and reports must start with the assigned prefix.: Custom Data ScreenID: DS121000

 

SiteMapNode | Shipment Details | DS501000

Custom screens and reports must start with the assigned prefix.: Shipment Details ScreenID: DS501000

3 replies

Steve Milner
Varsity III
Forum|alt.badge.img+6

@cmarshall74 The screen ID itself has to start with DSG. The validator checks your prefix against the start of the full 8-character ID, so DS131000 fails at the third character.

The Screen ID box isn't limited to two letters. Its mask is CC.CC.CC.CC, and every position accepts letters as well as digits. The dots are display only, so DS.G1.00.00 is stored as DSG10000 and passes. Acumatica ships IDs built this way too, like PMGI0010 and DBAP0001.

The page file still lands in Pages\DS. Create New Screen names that folder from the first two characters only, so it'll look the same as your current pages.

Your four existing screens need new IDs that start with DSG. Reports in the project get the same check against the report name.

Translate

Forum|alt.badge.img
  • Author
  • Freshman II
  • Nov 3, 2026 7:34 PM UTC

@cmarshall74 The screen ID itself has to start with DSG. The validator checks your prefix against the start of the full 8-character ID, so DS131000 fails at the third character.

The Screen ID box isn't limited to two letters. Its mask is CC.CC.CC.CC, and every position accepts letters as well as digits. The dots are display only, so DS.G1.00.00 is stored as DSG10000 and passes. Acumatica ships IDs built this way too, like PMGI0010 and DBAP0001.

The page file still lands in Pages\DS. Create New Screen names that folder from the first two characters only, so it'll look the same as your current pages.

Your four existing screens need new IDs that start with DSG. Reports in the project get the same check against the report name.

Thank you, for clarification for the 2 digits that would normally be in the second segment should we just use the first so 1 = Setup, etc?

Translate

Steve Milner
Varsity III
Forum|alt.badge.img+6

@cmarshall74 Yes, that works. The two-digit screen type (10 Setup, 20 Maintenance, 30 Data Entry, 40 Inquiry, 50 Processing, 60 Reports) is Acumatica's numbering guideline. The prefix validation doesn't check it. It only compares the first three characters to DSG.

Acumatica's own IDs with longer prefixes don't keep the type either. PMGI0010 and DBAP0001 just number in sequence.

Using the first digit keeps your IDs readable for anyone who knows the standard scheme. That leaves two digits for the screen number and two for the subscreen, so your first setup screen would be DSG10100.

Translate