Forum Discussion
Solved
Auto-Increment Number Field in a SharePoint List
I need to create an auto-increment field with a standard amount of digits. The format needs to be like this T000001, T000002, T000003, ......T000010, etc (7 Digits). When it gets to the 10th record it should not do this T0000010 (8 digits).
I tried using the popular, often referenced solution (link below). This method does not work as I hoped. If you put it in a format like this T1000, when it gets to the 10th item it does this T100010 rather than T10010.
Here is the popular solution I already tried: https://www.epmpartners.com.au/blog/how-to-create-an-auto-incrementing-number-field-in-a-sharepoint-list/
Hi Keenan (Ninjak), this complex auto-increment can be achieved relatively easily using 2 lists in SharePoint and a flow in Power Automate. The result will look like this in the main list which I've called Crop Harvest:
You will need a second list (which I've called Increment) to hold the next value. In the result above I manually changed the value to show the difference based on the number, and I've manually changed it back to 9 for now but you will see that it will auto-increment in the flow. This second list will only ever have 1 item which is the next value to be used:
In the flow the trigger I've used is When an item is created in the SharePoint main list.
Next we get the 1 item from the Increment list, and the next action is to initialize a string variable which I've named varIncrementNumber:
The next action to add is a Compose control which I've named ComposeNext and you select Next value from the dynamic content box on the right. What you will see when you do this is that it wraps itself in an apply to each control. It does this because although there is only 1 item in the Increment list there could potentially be lots so it adds the apply to each. That's fine, it's expected and you don't try to delete it but just leave it there.
The next action is a condition. For this first condition we are only going to test if the output of the previous compose action is less than 10 (we'll do the others shortly):
If it IS less than 10 then in the If yes green channel we add an Append to string variable and in the value type T00000 immediately followed by the output of the ComposeNext selected from the dynamic content box on the right:
If the ComposeNext value isn't less than 10 then in the red If no channel you add another condition. In the left hand box select the Output from the ComposeNext from the dynamic content, select is greater than or equal to, and then in the right hand box type 10. Then add another row and do the same but make it less than 100.
Again, you'll get a green if yes channel and a red if no channel. In the green channel, as before, add an append to string variable action and this time in the value add T0000 and then the output of the ComposeNext:
In the red If no channel add another condition as before but make it greater than or equal to 100 and less than 1000.
You keep doing that - changing the number of leading zeros each time of course - until you get to the last condition which is if the output of the ComposeNext is greater than or equal to 10000 and less than 100000 then you will add an Append to string variable in both channels. In the green If yes channel it will be T0 plus the Output and in the red if no channel it will be just T plus the Output.
So we've got the right value with the T plus correct leading zeros in our variable now. The next action is still inside the apply to each but not inside any of the conditions. The action is a SharePoint Update item action and in the text column where you are storing the increment text value you select the string variable varIncrementNumber. You'll see I've also stored the actual numeric value number from the ComposeNext:
We're almost at the end now and the next action is to add a Compose and add 1 to the ComposeNext value. So for this we use an expression of add (outputs('ComposeNext'),1). Finally we use the output of that to update the Increment list:
Whatever value you have in the Increment list the flow will check that and apply the T and the correct number of zeros and then the increment value. It will take just 2 or 3 seconds to do this and to update the main list and the increment list.
That took far longer to write out and do the screenshots than it took to prepare the SharePoint lists and do the flow!!
Do come back with questions about any of this.Rob
Los GallardosMicrosoft Power Automate Community Super User
Ninjak I realise this post is over a year old but thought it is worth highlighting that there is now a Format Number action that should make this process a lot more simple:
Ninjakfor SharePoint server, you can't used Microsoft automate without using gateway.
Instead, you should use JSOM or SharePoint Designer!
Hi Keenan (Ninjak), this complex auto-increment can be achieved relatively easily using 2 lists in SharePoint and a flow in Power Automate. The result will look like this in the main list which I've called Crop Harvest:
You will need a second list (which I've called Increment) to hold the next value. In the result above I manually changed the value to show the difference based on the number, and I've manually changed it back to 9 for now but you will see that it will auto-increment in the flow. This second list will only ever have 1 item which is the next value to be used:
In the flow the trigger I've used is When an item is created in the SharePoint main list.
Next we get the 1 item from the Increment list, and the next action is to initialize a string variable which I've named varIncrementNumber:
The next action to add is a Compose control which I've named ComposeNext and you select Next value from the dynamic content box on the right. What you will see when you do this is that it wraps itself in an apply to each control. It does this because although there is only 1 item in the Increment list there could potentially be lots so it adds the apply to each. That's fine, it's expected and you don't try to delete it but just leave it there.
The next action is a condition. For this first condition we are only going to test if the output of the previous compose action is less than 10 (we'll do the others shortly):
If it IS less than 10 then in the If yes green channel we add an Append to string variable and in the value type T00000 immediately followed by the output of the ComposeNext selected from the dynamic content box on the right:
If the ComposeNext value isn't less than 10 then in the red If no channel you add another condition. In the left hand box select the Output from the ComposeNext from the dynamic content, select is greater than or equal to, and then in the right hand box type 10. Then add another row and do the same but make it less than 100.
Again, you'll get a green if yes channel and a red if no channel. In the green channel, as before, add an append to string variable action and this time in the value add T0000 and then the output of the ComposeNext:
In the red If no channel add another condition as before but make it greater than or equal to 100 and less than 1000.
You keep doing that - changing the number of leading zeros each time of course - until you get to the last condition which is if the output of the ComposeNext is greater than or equal to 10000 and less than 100000 then you will add an Append to string variable in both channels. In the green If yes channel it will be T0 plus the Output and in the red if no channel it will be just T plus the Output.
So we've got the right value with the T plus correct leading zeros in our variable now. The next action is still inside the apply to each but not inside any of the conditions. The action is a SharePoint Update item action and in the text column where you are storing the increment text value you select the string variable varIncrementNumber. You'll see I've also stored the actual numeric value number from the ComposeNext:
We're almost at the end now and the next action is to add a Compose and add 1 to the ComposeNext value. So for this we use an expression of add (outputs('ComposeNext'),1). Finally we use the output of that to update the Increment list:
Whatever value you have in the Increment list the flow will check that and apply the T and the correct number of zeros and then the increment value. It will take just 2 or 3 seconds to do this and to update the main list and the increment list.
That took far longer to write out and do the screenshots than it took to prepare the SharePoint lists and do the flow!!
Do come back with questions about any of this.Rob
Los GallardosMicrosoft Power Automate Community Super User
RobElliott Hi, many thanks for the insightful and inspiring explanation.
I would wonder if this short formula for a calculated column that should fix the issue
="T"&TEXT([Increment],"0000000")
Kind regards,
Tan
I realize that this thread is over a year old. But I have had this bookmarked and attempted to make this work multiples times over the past 6 months. I finally was able to figure out where I went wrong and got it to work.
So after it finally working on a fresh list, I decided that I would bring in my already created log file and put all those logs in there and update my Increment list to be the next value. I then set my flow to be active. And it worked....but it keeps looping through my already created list values.
Where should I begin looking to stop the flow from auto running even though I have not clicked the create new in my sharepoint list? Please help as I have had over 2000 flows run in the last hour.
JamesC007. Rob's post was great, but since he wrote it, a new "FormatNumber" option became available which makes things much easier. I've screenshotted the following from a real working scenario we use internally:
First, set the AutoNumber variable and grab the current AutoNumber single List Item:
Then, in a For Each loop, increment the variable, and format using the Format Number action. Note the number format string is stored in the List, screenshot further down. (The Update Projects List Item just applies the current number to our separate project list)
Note that the way we do this is to store the next available number in our list, apply the next number, then increment afterwards.Finally, update the incremented number into the AutoNumber list item:
Note, the reason we're not getting any infinite loops is that we only trigger this whole flow when an item (or file, depending on list or library) is created. It is important to not use the "Created or Modified" otherwise the action that updates the number on your target document or list item will continually fire...you could use a Trigger condition to resolve that, but it's easier to just use the "is created" trigger.
If you needed to apply an auto-number as a one off to a historical set of list items, then you could create a separate flow with a manual trigger that you only run once, that filters all your items/documents then uses a foreach to apply the above logic. In that scenario you would need to make sure you set your loop concurrency to 1 only, to allow the number to increment correctly.
Quick look at the AutoNumber list, contains a single item as follows:
Note from above, the NumberFormat is a string value, in the above case "00000" indicating a 5 character length...add more or less zeros to determine the length of the string
Hope that helps
- Brilliant. That works like a champ, thanks!
Ninjak have you tried using a Calculated field?
In your list or library, the ID column (a system column) will increment each time an item is added. You can use a calculated column to create a prefix and append the ID e.g. T000+ID
SteveKnutson This is the approach I tried. Essentially:
NewID =TEXT(1383+ID,"0")
My list was created by importing a bunch of data from an Access DB (via Excel), and I wanted a new ID number that would start after the ID numbers from the data I had used - thus the 1383, which combined with the number of records, would mean that my next ID number would be 2001.
It worked. Until the next time I logged in, and all of the NewIDs across all records was 1383. So I edited the formulas, put brackets around ID, and it worked again. Until the next time I logged in, and all of the NewIds across all records was 1383. So I ... well, you get it.
Any idea why the formula keeps not including the ID value?
how can I do that ,
i want a formula to add+1 each time I adda taskSteveKnutson
