I have a Sharepoint list in which employees write personnel applications using Power Apps.
One of the fields is the application date, which is set automatically by Power Apps.
Now, when a new entry is created in the list, I want to use Power Automate to automatically generate a unique ID, which is composed as follows:
YYYY ID, example:
2023-1
2023-2
...
2024-1
Now comes the special part of my request. I have an old list, which was previously kept using Excel. This also includes applications from previous years, which I need to migrate.
Now this ID should also be generated during the migration. For example, today 02.03.2023 I enter an application in the list whose application date is 22.11.2022 as an example.
Now I want to see what the last ID was in 2022 and then number it consecutively.
So it could be that there is an application 2022-45, and the new application of 22.11.2022 should then be numbered 2022-46.
Who can help me?
Solved! Go to Solution.
@MircoKunz82 I've built a flow to handle new items being created and getting a unique ID as per your requirements. When you move the other older items across, they should automatically get a unique ID generated as part of this flow. Hopefully this is what you're looking for.
For this example, I'm using the following List.
The full flow is below. I'll go into each of the actions.
When an item is created will trigger when we add a new item.
Because we can create/upload multiple items, we don't want multiple flows running at the same time, otherwise we might get duplicate unique IDs generated. To avoid this, we can turn on Concurrency Control on our trigger and set the Degree of Parallelism to 1 so the trigger will only run once the previous flow has completed (avoiding any overlapping).
Get items will return the last item that was created in the same year as the current item. It will order the results in descending order based on Application ID, set to only return 1 item, and uses the following expression for the Filter Query to exclude the current item and get items within the year of the current item's Application Date.
//Filter Query
ID ne @{triggerOutputs()?['body/ID']} and ApplicationDate ge '@{formatDateTime(triggerOutputs()?['body/ApplicationDate'], 'yyyy-01-01')}' and ApplicationDate le '@{formatDateTime(triggerOutputs()?['body/ApplicationDate'], 'yyyy-12-31')}'
//Order By
ApplicationID desc
//Top Count
1
Initialize variable creates a variable called Number of type Integer and sets the initial value to 1. This number will end up being appended to the current year to give us the unique ID.
Condition checks to see if any items were returned from Get items. If no items were returned, then we can assume there were no existing items in the List from the item's Application Date year, so we use the current number set for our Number variable. However, if there was an item returned, we get the number part of the unique ID, add 1 to it, then set that as the new value of Number. The expression used in the Condition is below:
length(outputs('Get_items')?['body/value'])
The expression to get the number part of the unique ID and add 1 to it is below:
add(int(slice(first(outputs('Get_items')?['body/value'])?['ApplicationID'], 5)), 1)
Update item uses the ID from our trigger to get the current item and updates the Title (from our trigger) and the ApplicationID using the following expression:
concat(formatDateTime(triggerOutputs()?['body/ApplicationDate'], 'yyyy'), '-', variables('Number'))
----------------------------------------------------------------------
If I've answered your question, please mark the post as Solved.
If you like my response, please consider giving it a Thumbs Up.
@MircoKunz82 I've built a flow to handle new items being created and getting a unique ID as per your requirements. When you move the other older items across, they should automatically get a unique ID generated as part of this flow. Hopefully this is what you're looking for.
For this example, I'm using the following List.
The full flow is below. I'll go into each of the actions.
When an item is created will trigger when we add a new item.
Because we can create/upload multiple items, we don't want multiple flows running at the same time, otherwise we might get duplicate unique IDs generated. To avoid this, we can turn on Concurrency Control on our trigger and set the Degree of Parallelism to 1 so the trigger will only run once the previous flow has completed (avoiding any overlapping).
Get items will return the last item that was created in the same year as the current item. It will order the results in descending order based on Application ID, set to only return 1 item, and uses the following expression for the Filter Query to exclude the current item and get items within the year of the current item's Application Date.
//Filter Query
ID ne @{triggerOutputs()?['body/ID']} and ApplicationDate ge '@{formatDateTime(triggerOutputs()?['body/ApplicationDate'], 'yyyy-01-01')}' and ApplicationDate le '@{formatDateTime(triggerOutputs()?['body/ApplicationDate'], 'yyyy-12-31')}'
//Order By
ApplicationID desc
//Top Count
1
Initialize variable creates a variable called Number of type Integer and sets the initial value to 1. This number will end up being appended to the current year to give us the unique ID.
Condition checks to see if any items were returned from Get items. If no items were returned, then we can assume there were no existing items in the List from the item's Application Date year, so we use the current number set for our Number variable. However, if there was an item returned, we get the number part of the unique ID, add 1 to it, then set that as the new value of Number. The expression used in the Condition is below:
length(outputs('Get_items')?['body/value'])
The expression to get the number part of the unique ID and add 1 to it is below:
add(int(slice(first(outputs('Get_items')?['body/value'])?['ApplicationID'], 5)), 1)
Update item uses the ID from our trigger to get the current item and updates the Title (from our trigger) and the ApplicationID using the following expression:
concat(formatDateTime(triggerOutputs()?['body/ApplicationDate'], 'yyyy'), '-', variables('Number'))
----------------------------------------------------------------------
If I've answered your question, please mark the post as Solved.
If you like my response, please consider giving it a Thumbs Up.
Hi,
Does someone ran into this error with the solution of @grantjenkins :
InvalidTemplate. Unable to process template language expressions in action 'Get_items' inputs at line '0' and column '0': 'The template language function 'parseDateTime' expects its first parameter to be of type string. The provided value is of type 'Null'. Please see https://aka.ms/logicexpressions#parsedatetime for usage details.'.
Hi @Martin_V ,
i have the same issue. Do you have another way, or know the what is wrong?
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24 17 @Anil_g 7 @ManishSolanki 13 @eetuRobo 5 @David_MA 10 @VishnuReddy1997 5 @SpongYe 9JhonatanOB19932 (tie) @Nived_Nambiar 8 @maltie 2 (tie) @PA-Noob 2 (tie) @LukeMcG 2 (tie) @tgut03 2 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate @Deenuji 12@ManishSolanki 19 @Anil_g 10 @NathanAlvares24 17 @VishnuReddy1997 6 @Expiscornovus 10 @Tjan 5 @Nived_Nambiar 10 @eetuRobo 3 @SudeepGhatakNZ 8 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2 Anil_g2 SharonS2
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages