Applies to Product - Microsoft Dataverse
What’s happening?
Autonumbering seed value is not deploying correctly to the target production environment after a deployment, while it appears to function as expected in the UAT environment.
Autonumbering seed value is not deploying correctly to the target production environment after a deployment, while it appears to function as expected in the UAT environment.
Reason:
This is an expected behavior. Setting the seed only modifies the given attribute's current number value in the current environment. When a solution is imported into a new environment, the seed value does not carry over.
This is an expected behavior. Setting the seed only modifies the given attribute's current number value in the current environment. When a solution is imported into a new environment, the seed value does not carry over.
Resolution:
To resolve this, the seed value needs to be changed directly in the target organization. Additionally, an alternative workaround is to export the AutoNumber field as an unmanaged solution and then import it, which allows for manual changes to the seed value. For further reference, please consult the documentation on creating auto-number attributes.
To resolve this, the seed value needs to be changed directly in the target organization. Additionally, an alternative workaround is to export the AutoNumber field as an unmanaged solution and then import it, which allows for manual changes to the seed value. For further reference, please consult the documentation on creating auto-number attributes.