Generated number in powerapps needs to be locked in dataverse

[RealMABN]

Hi all,

We have made a function in our Powerapp that makes it possible to generate the lowest number available in one of our Dataverse column. The problem that we face is that the app is meant to be used by multiple people and at some point we will run into a situation, where two users will have generated the same number and then submitted a Dataverse form with it, when the number should be unique for each record. 

We were thinking about creating a record with number when its generated and then delete the record when we submit the "real" form. But I feel like this is a duct tape solution, and want to hear you guys if you could come up with another solution 🙂

Thanks in advance.

[gabibalaban · Accepted solution]

@RealMABN ,

The  generate number process should be done at submission time, not earlier. The user will be aware about this number after the successful save.     

[VJR · Accepted solution]

- If its possible generate the lowest number during the final Submit.

- Another option is during the final submit, have a check function that will check if the newly generated number is already in any of the submitted records column. If yes, find the next lowest available number.

[RealMABN]

Thanks for the suggestions. I will try and see if it works for us! 🙂