@tagustin2020
So you're going with a combination of #2 and #3. The first part is to assign the number in flow, but in order to then get that updated in your datasource, you'll need the expensive refresh on the record...and you'll need to get that after the flow completes.
<I'm going to ramble here for just a bit...>
I will throw one other thing out there...sequential numbering is a thing of the past! It is based on the old paper system where each sheet of a form was numbered sequentially. Somehow that ancient principal has perpetuated even into today, but, and I only mention this to say...stop! Do you really need a sequential number? If there is some essential business process that requires it, then you have no choice. But, if there is not, then why try to continue it?
We abandoned sequential numbering in all our systems and apps over a decade ago because it really had not informational value. What we went with was more of a date-based numbering such as yymmddhhmmss. Why this? Because it actually provides value. Unlike a sequential number such as 10030 that provides no real information, this at least provides an exact time of when the artifact was created. If I pick up an item that 10030 on it, I have no idea if this is old or new or what unless I look it up. If I pick up an item that has 1902071233 on it, I immediately know that this is two years old.
In most cases we only trail down to the seconds in high load apps. If there is very minimal risk of a person creating two within the same minute, we skip the seconds. Likewise if there is not chance of two records being created in the same hour, se skip the minutes...and so on.
This provides not only valuable information from the unique ID, but it also plays VERY nicely with PowerApps as there is no flow needed nor and issues with refreshing, writing back, etc. Just submit and the value exists. Done.
Okay...</end rambling here>
Now, back to the story...I believe you might have misunderstood my options (and I might have mislead in number 2). I gave those for the purpose of specifically meeting the requirement of displaying the Sequential ID AT the time the user is creating the item - that seemed to be what you wanted. And looking back, #2 would not technically have done that (although for some reason that was in my mind).
So, that brings me to the conclusion that since you chose flow, that showing the Sequential ID at the time the user enters the new record is NOT that important.
In that case I would very much discontinue the use of flow for this. You will cost your app more performance issues and complexity than is necessary.
Instead, simply change your OnSuccess action of your form to the following:
UpdateIf(yourList, ID=Self.LastSubmit.ID, {'Request Number': Self.LastSubmit.ID + 10000})
That will do the equivalent of the flow without the cost. And your Gallery will immediately reflect it without any further action.
Keeping in mind, that this is based on what you are currently trying, which implies that displaying the Request number to the user before the new record is created is no longer necessary.
Beyond that...if you want the option to display the number at creation time, I'd think through my rambling above a bit...it's a real clean and easy solution. I will add to it, that doing searching on that scheme play really well in PowerApps - ex. Filter(data, RequestNumber>=2000000000 && RequestNumber<=2012312359) will give me all the records in the year 2000. Or, Filter(data, RequestNumber>=2006000000 && RequestNumber<=2006302359) would give me all records in June 2020. etc...
Two birds, one stone!
