Issue:
When using autonumbering for accounts or any other entity, the autonumbering begins to duplicate.
Cause:
There are a few root causes to this.
- If records are imported into the CRM for the first time with a number that is traditionally auto generated but was manually entered, the value will be duplicated.
- This can also occur when a process within your system "clones" a record including the auto number value.
Resolution:
- For cases where there has been an import of records with manually entered values in the Auto-numbering field, adjust the seed number within the auto-numbering rule to above the highest value imported. Then resolve duplicate values with unused values under the new seed number or with alpha-numeric values not in line with the auto-numbering.
- Navigate to https://make.powerapps.com/
- Confirm the environment to make the changes.
3. Navigate to Solutions Tab
4. Search "default" or scroll to the bottom to access the Default Solution.
5. Use the search in the upper right hand corner to find the Table/Entity of the field you are looking for.
6. Find the field within the columns list within the Table/Entity.
7. Update the Seed Value. This will set the next number in the Auto numbering chain. If, for example, the highest Account Number is 54321, You would want to set the Seed Value to 54322 or higher.
8. With the Seed Value set, the next goal would be resolving duplication.
If the duplication started due to an import, all potential duplicates should appear in a search of records created On or After the date of the import and whose Auto Number value is less than or equal to most recently created record before the new seed value was set. Duplicate values can be replaced by either a value that has be deprecated for use in your autonumbering, for example if account 1234 was deleted and is no longer in your systems anywhere, that value may be safe for use in resolving the duplicates. Alternatively an alpha character prefix or suffix could be added to distinguish the values. For Example, account 9876 could be changed to 9876A.
- For cases where a record is "cloned" be sure to omit the autonumbering as part of the fields carried over unless a duplicate value is desire.