Share
ReportHi!
We have a workflow that triggers when a contact record is created. This workflow then implements a custom made auto number field that is increased with each new contact. A decision was made to replace our own implementation of an autonumber field to use the built in feature available in version 9. I added an extra step in the workflow to create a record with the built in autonumber. I used Xrmtoolbox autonumber manager to set the seed and everything. I seemed to work good in the manual tests. But as soon as a non-admin user created a contact the workflow failed; because I forgot to update the permissions to create the new custom entity (we use a specific entity for the autonumber but it should not matter with regards to my question). After I fixed the permissions and the user again tried to create a contact it worked, no fails in the workflow. But at this point the built in autonumber and our own implementation differed by the X number of times the user failed the workflow. It seems as if the autonumber increases even though the record is never created. Is this the intended functionality or is this a bug?
Just to get some things out of the way: I am sure no records (with built in autonumber) were created and remained after the workflow. I am also sure I set the seed correctly.
So in short: If user doesn't have permission to create a custom entity (in my case) and a workflow run with the user's permissions tries to create the custom entity and the creation fails, the built in autonumber still increases in value.
Thanks in advance!
All responses (
Answers (
40,876
