cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
mvdb
Advocate I
Advocate I

Reset autonumber each year (if possible via script that searches in dataverse)

I have a autonumber fielde with as prefix the current year and the sequence are 4 digits starting with 0001. Next January, the prefix will change and the first autonumber of the year will be 2022-0210, but I want it to reset to 0001 so the autonumber will be 2022-0001. I've read that there is no standard solution for this. I've read something about external tools like North52 or Auto Number Manager. On the other hand I'm thinking of writing an OnLoad-script that searches if there are already existing records made in the current year and fill in a custom autonumber of reset the seed while using the script. But for this I'll need to access the Dataverse-tables from within the form(-script) and I don't know how to do this at the moment.

 

What method would be easiest, and how should I tackle this problem? And how can I search in dataverse-tables from within a form-script? Thank you.

1 ACCEPTED SOLUTION

Accepted Solutions
EricRegnier
Most Valuable Professional
Most Valuable Professional

Hi @mvdb,

I wouldn't go the JavaScript route for these main reasons:

  1. you still want the auto number to be set if the records are update outside the main form
  2. you can't guarantee uniqueness of your auto number (e.g. 2 records are open at the same time might have the same number)
  3. as your table grows it wouldn't scale well as the loading time of your form will increase to look at all the records.

The out-of-the-box auto numbering feature will not allow you reset the seed/count. You need to handle this in a custom method with sync plugins and ensure uniqueness by locking the row until the new auto number is updated and committed. High-level logic:

  1. Have a separate table/entity (i.e named AutoNumberConfig) that keeps track of the current sequence, year and a lock column/field.
  2. In the auto number plugin, 1st thing is to update the lock field (generate a new guid) in AutoNumberConfig record. This will lock the row so if another record is created at the same time will wait until this row is done.
  3. Then in you auto numbering logic, check if the current year is different from the last save year. If so reset the sequence otherwise increment the sequence.
  4. Save current record with the auto number and AutoNumberConfig row with the year and sequence.

Here's a good article explain how to achieve this: https://us.hso.com/blog/how-to-implement-robust-auto-numbering-using-transactions-in-microsoft-dynam... 

Hope this helps!

 

View solution in original post

5 REPLIES 5
dpoggemann
Most Valuable Professional
Most Valuable Professional

Hi @mvdb,

 

I have done a similar approach with other customers and really accomplished this in a different way.  I utilized the auto-number fields as they are and utilized a separate field (many times the default Name field) on the table and set this value based on other fields with real-time workflows.  This allows me to have that field change over time if specific values change that drive the value in the unique identifier.

 

The real time workflow approach will execute any time the values change or the record is created.

 

Hope this helps!  Please mark accepted if answers your question or like if helped.

 

Thanks,


Drew

 

Hope this helps. Please accept if answers your question or Like if helps in any way.
Thanks,
Drew
EricRegnier
Most Valuable Professional
Most Valuable Professional

Hi @mvdb,

I wouldn't go the JavaScript route for these main reasons:

  1. you still want the auto number to be set if the records are update outside the main form
  2. you can't guarantee uniqueness of your auto number (e.g. 2 records are open at the same time might have the same number)
  3. as your table grows it wouldn't scale well as the loading time of your form will increase to look at all the records.

The out-of-the-box auto numbering feature will not allow you reset the seed/count. You need to handle this in a custom method with sync plugins and ensure uniqueness by locking the row until the new auto number is updated and committed. High-level logic:

  1. Have a separate table/entity (i.e named AutoNumberConfig) that keeps track of the current sequence, year and a lock column/field.
  2. In the auto number plugin, 1st thing is to update the lock field (generate a new guid) in AutoNumberConfig record. This will lock the row so if another record is created at the same time will wait until this row is done.
  3. Then in you auto numbering logic, check if the current year is different from the last save year. If so reset the sequence otherwise increment the sequence.
  4. Save current record with the auto number and AutoNumberConfig row with the year and sequence.

Here's a good article explain how to achieve this: https://us.hso.com/blog/how-to-implement-robust-auto-numbering-using-transactions-in-microsoft-dynam... 

Hope this helps!

 

AlexG7522
Frequent Visitor

Another option is to use the unbound action SetAutoNumberSeed via power automate

I can confirm, that PowerAutomate will do the work. You can set the autonumber to any value.

In my Example, next Invoice number will be INV-4001356-xxx

You could run such flow on demand or on schedule

 

  Screenshot 2022-02-01 at 13.21.53.png

Unfortunately, resetting an autonumber each year is not a built-in feature in most software. However, there are several workarounds to achieve the desired functionality:

1. Scripting:

  • Power Automate (Microsoft Dataverse): You can use Power Automate to create a flow that triggers on record creation. The flow can then check the current year and reset the autonumber seed if it's a new year. This approach requires some technical knowledge and may not scale well for large datasets.
  • Airtable: Airtable supports formulas and scripts that can be used to manipulate data. You can create a formula that combines the current year with a sequential number, effectively resetting the numbering each year.
  • JavaScript/Plugins: In some platforms like SharePoint lists, you can use JavaScript or custom plugins to achieve this functionality. This approach requires advanced coding skills and is not recommended for beginners.

2. Separate AutoNumber Field:

  • Microsoft Dataverse: Create a separate field for the autonumber that automatically resets each year. This field can be calculated based on the current year and a sequential number.
  • Airtable: Create a separate field for the year and use a formula to combine it with a sequential number.

3. Third-party Tools:

  • North52 AutoNumber Manager: This is a popular add-on for Microsoft Dataverse that provides advanced autonumbering features, including reset options.
  • Other platform-specific tools: Several third-party tools offer similar functionality for different platforms.

Here are some additional factors to consider:

  • Data integrity: When implementing any workaround, ensure data integrity by avoiding duplicate numbers and maintaining consistency across records.
  • Performance: Scripting solutions may impact performance, especially with large datasets. Choose an approach that scales well for your needs.
  • Technical expertise: Some methods require coding knowledge. Choose a solution that aligns with your technical skills.

Before implementing any solution, carefully assess your specific needs, technical resources, and platform limitations to determine the most suitable approach for resetting your autonumber each year.

 

DynaTech Systems

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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 in the Forums 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 of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (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. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     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 Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     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 Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

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.    

Updates to Transitions in the Power Platform Communities

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

Users online (1,685)