Jonas “The Shuffler” Rapp reports: when modifying autonumbering for built-in entities like case, always include a dash in the pattern to stop Dynamics 365 from self-combusting.
The Auto Number Format of the Case Number (ticketnumber) attribute on the Case (incident) entity had been changed from the default value:
To a custom format:
And now it was no longer possible to open the Auto-Numbering dialog in Dynamics 365.
I see four potential problems here:
- The prefix is four characters – will that fit?
- There is no dash between prefix and number
- The number is seven digits long
- There is no random string at the end
After some investigation using the number one troubleshooting methodology – some simple trial-and-error – I came to some conclusions:
- Prefix may be even longer than that, I tried with CASENUMBER and that worked fine too
- Skipping the dash makes the dialog explode like above
- Seven digits works fine, even though the UI in the dialog will only show 6, there is no 7 available
- Works fine without random string, but in the dialog it still looks like it has the random suffix
So make sure you keep a DASH between your prefix and number when you are changing Auto Number Format for out of the box number attributes!