Hi Jonas,

not all entities in solution will be displayed in autonummanger, so they cant be choosen.
any idea?
thx.
sincerly peter

Hi,
We have configured Auto Number to Case Entity in the
CASE-{DATETIMEUTC:ddMMyyyy}-{SEQNUM:4} format. we have noticed sometimes the sequence number is not generated in the sequential way instead it is jumping. Is there any specific setting we need to do make it work properly and also wanted to understand how this format will overwrite the existing system format, is there any plugin registered when we set the configuration. please let us know.

Example.
Case 1 : CASE-22012020-0001
Case 2 : CASE-22012020-0002
Case 3 : CASE-22012020-0005
Case 4 : CASE-22012020-0006
Case 5 : CASE-22012020-0007
Case 6 : CASE-22012020-0008
Case 7 : CASE-22012020-0013
Case 8 : CASE-22012020-0014

Hi,

after I changed the Numberformat to {DATETIMEUTC:yy}-{SEQNUM:5}-{RANDSTRING:6} instead of 19-{SEQNUM:5}-{RANDSTRING:6} I can't access the autonumbering in CRM anymore. Error is the generic CRM error: please try again...contact your administrator. When i switch back it works again.

Any Ideas what could be causing this?

Thanks,
Jan

Under the attributes there is a field marked "Advanced 'Don't require SEQNUM'". This appears to have been added in a later version than the one the screenshots were taken in.

When creating a new auto-number attribute on a custom entity I get the following error message:

Save attribute failed: System.ServiceModel.FaultException‘1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: Languageld should not be null. (Fault Detail is equal to Exception details: ErrorCode: 0x80040203 Message: Languageld should not be null. TimeStamp: 2019-10-1ST08201:20.6321913Z Exception details: ErrorCode: 0x80040203 Message: Languageld should not be null. TimeStamp: 2019-10-15T08:01:20.6321913Z Exception details: ErrorCode: 0x80040216 Message: System.ArgumentNullException: Value cannot be null. Parameter name: Languageld should not be null. TimeStamp: 2019-10-15T08:01:20.6321913Z ).

The base language and user language is both set to Dutch (LCID 1043). No other language packs are enabled in this org.

While trying to update existing auto-number field , facing the error "Seed is not a valid number".
Attached screenshot for reference.

I tried updating an existing auto-number attribute and figured out that neither description and field length get updated. And I need to update the field length.

I've now updated the field length through dynamics customization.

Would it be a good way to never allow saving of an attribute when the length doesn't match the format? So we would always avoid later exceptions in the form of "string size exceeds limit".

Anyway great work and many thanks!

Hello, I set a field as an auto-numbering field and then tried to undo the customization by removing the sequence and updating the field. I received an "Unhandled Exception" error and now every view that the field was referencing has become in-editable and I cannot even remove the field from the system views to remove the dependencies and delete the field. Is there a better way to undo the auto-numbering on a field without error, or fix my views so I can delete the dependencies and the field and try again with a new one? Thank you, Kevin

I installed Auto numbering Plugin from xrmtoolbox i select opportunity entity then i entered the auto numbering format when i click update everything end successfully but when create new opportunity in my online instance nothing happens

Removing autonumber fails.
The dialog pops up asking to confirm removal of the autonumber property. Then throws an unhandled exception " Format string must contain a {SEQNUM:n} placeholder.". Looks ParseFormatSEQNUM method does not allow for empty string.

I it possible to populate part of the autonumber as the opportunity that generated an order, then reset the seed of the orders for the next opportunity

OPP0001 - 001
OPP0001 - 002

OPP0002 - 001

We have successfully adjusted the seed to 500000 on standard entity case auto number.
When now 'Guessing current SEQNUM' the value returned is 50000.

Seems to be an display issue.
Auto Number Manager Version 1.2018.8.1

Hi Jonas,
I have used auto numbering in one of the entities and it works fine for the newly created records. But the challenge I face is with existing records. I need to update the existing records and the existing records does not have a number on them.
I have searched for this and could not find a solution. I really appreciate if you could guide me with any solution.

Thanks
Sanjaya

Example account:
Create one sequence for account type customer, and one sequence for account type vendor?

I only want to write to one field, and not have to use workflow afterword to replace the "account number" field.

Probably not supported by the sdk directly, but needed to ask if possible adding the if in the beginning :)

I spun up a new D365O trial (9.0.2.1470) and configured the account.accountnumber field as per the attached screenshot, but when I create a new account record the accountnumber field is not assigned an auto-number.

Hi, when trying to install "Auto Number Manager" I get message "Auto Number Manager incompatible with the current version of XrmToolBox". In XrmToolBox I selected "About" -> "Checked for update" and got result "No update available!"

Also "Auto Number Manager" text was red in Plugins Store. Not sure what to do, is it something on my end or maybe something else? ;-)

Thanks in advance!

Hi @rappen

If the record is created in Dynamics 365, the autonumber is generated in the desired field.
If the record is created from Dynamics Portals, the autonumber is not generated in the desired field.

It's started generating duplicate values i.e. XXXX1120. There are existing records in CRM with values until XXXX2428.

Any idea on how to fix it so the number starts with XXXX2429 not XXXX1121

Reproduction Steps:

1. Create a field with field level security enabled for a record.

2. Create a field security profile for full access to that field.

3. Add the current user to that field security profile

4. Attempt to create a record (This should work).

5. Add auto number attributes to the newly created field using the XRM toolbox add-in.

6. Attempt to create another record. This time the following error will occur:

“The user does not have create permissions to a secured field. The requested operation could not be completed. If you contact support, please provide the technical details.”

7. The field also disappears from the list of fields that have field level security enabled on.

Notes:
I believe the issue is caused by not retrieving the existing attribute metadata before calling the update attribute request.

I don't encounter the same problem when using the following code from a console application.

        private static void AddAutoNumberToExistingField(string entityName, string fieldName, string autoNumberFormat, int seedValue = 0)
        {
            // Create the retrieve request
            RetrieveAttributeRequest attributeRequest = new RetrieveAttributeRequest
            {
                EntityLogicalName = entityName,
                LogicalName = fieldName,
                RetrieveAsIfPublished = true
            };
            // Retrieve attribute response
            RetrieveAttributeResponse attributeResponse = (RetrieveAttributeResponse)_client.Execute(attributeRequest);

            //Modify the retrieved auto-number attribute
            AttributeMetadata retrievedAttributeMetadata = attributeResponse.AttributeMetadata;
            retrievedAttributeMetadata.AutoNumberFormat = autoNumberFormat; //Modify the existing attribute by writing the format as per your requirement 

            // Update the auto-number attribute            
            UpdateAttributeRequest updateRequest = new UpdateAttributeRequest
            {
                Attribute = retrievedAttributeMetadata,
                EntityName = entityName
            };
            // Execute the update attribute request
            _client.Execute(updateRequest);

            if (seedValue > 0)
            {
                // Set the auto number seed value
                SetAutoNumberSeedRequest setSeedValueRequest = new SetAutoNumberSeedRequest();
                setSeedValueRequest.EntityName = entityName;
                setSeedValueRequest.AttributeName = fieldName;
                setSeedValueRequest.Value = seedValue;
                _client.Execute(setSeedValueRequest);
            }
        }

After creating connection, at least one unmanaged solution is missing from the solution dropdown list. In general the connection seems to work as there are close to 100 solutions available (about the correct amount, didn't yet count if my target solution is the only one missing). Any advice if this is just some simple user error?

Appreciate the seed number guessing is probably not 100% accurate, however it seems way off - I just updated 3 tables with a new auto number, and used your trick with a separate entity to update the autonumbers, however when re-setting the seed to the next value (as I massively underestimated it initially), the ANM guessed value was about 50 - 500 records out.

Whereas when I sorted the autonumber column A-Z, it was clear there were higher numbers than the guess.

Example at the lower end
A-Z sorted Auto num

Autonum guess

Example at the higher end
A-Z sorted Auto num

Autonum guess

What I did:
Created a new autonumber, set length to 100, selected {SEQNUM:1}, and updated.
What I expected:
When a new opportunity was created, the number would start at 0 or 1
What happened:
The number started at 1000

When opening existing auto number the display name is not collected, so you have to remember it and type it in manually.
Only happens on a newly created field, works like expected on existing fields

I had a requirement to have an autonumber start at 6billion. Unfortunately the tool does not allow a seed that high. I was able to successfully create a console app and set the seed and it works fine. Is it possible to update the tool?

Hi there,

We encountered an issue where the seed counter "jumps" up quite a few counters between consective records (XXX-607 to XXX-632) without any explanation. We have checked the audit summaries and server logs but there seem to be no explanation as to why or how this occur.

Can you think of how this could possibly occur? So far it's happened only once.

I'll try and see if I can get a screenshot if you think it might help.

Thank you and best regards.

Hi Jonas,

I was trying to change the seed of the OOB Quote Number field for a customer who just upgraded to v9, however AutoNumberManager returns an error when I confirm this change.

Should this be possible with the AutoNumberManager? It would be pretty nice to be able to do, to work around the inability to override the seed in the UI...

Many thanks,
Anton

Hi,

I have enabled auto-numbering on a primary field on a custom entity and subsequently disabled the auto numbering because there are old records that require to be added to the custom entity records.

The attribute remained locked in the form after I have disabled the auto-numbering feature. I have tried to unlock using OOB attribute properties and also using Bulk Form Attribute Manager from XRMToolbox but it failed to unlock it.

Pls help.