I am creating a database that needs an ID number called proposal number that continues from the already existing proposal numbers.
I know that there are limitations to how ID numbers work so I have thought of a work around but need help putting it in place.
When a person enters a name into the new entry it automatically saves. Saving gives it an ID number in sharepoint, so after this a label is shown for the proposal number that is calculated by ID number + 170008 (this is a constant number).
Then that proposal number that is calculated from the ID number would get saved in a column.
I hope I articulated that properly, there are a couple places I'm having trouble with. The autosave after the name is entered, and the subsequent proposal ID popping up and updating.
Thank you
Solved! Go to Solution.
Hi @rowlinx, what you say is now clearer, thank you.
First of all a bit of background, apologies if this is clear to you already: SharePoint will only create a new ID when a new record is created. There is no way to 'ask' SharePoint what the new ID will be for a future new record or to reserve one.
Having considered this, are you absolutely sure that you want to create the new ID only with partial data in the new record?
I am asking this because normally a database would have conditions on columns (such as columns which require data etc., conditions on dates etc.) which are very good practice to keep data integrity. So if you create a partial record only to get its ID, then you need dummy data to make the partial record acceptable to the database. Also, please consider that if the app or the device or the user stops what they are doing then you are left with an incomplete record in the database.
If you are still convinced that you need a new ID before the record is completely created, then the easiest way is to have an action linked to a data input in the first box that creates and retrieves a new record. What shape this action takes depends on what the first control is (i.e. text input or drop down etc.) and if you are using a new item form. For example you could use an OnUpdate property of a control with a submit form action. The ID box could simply display ID+170008 by default.
Sorry I cannot be more specific, but hopefully I have given you some pointers.
If you use a Patch function to write to SP then just use ClearCollect(MyPatchedItem, Patch(SP_source, Defaults(SP_source), {record data here}))
Then MyPatchedItem will contain the ID column with the attributed ID.
If you use PowerApps edit forms (ugh...) then I think there is functionality to return the latest submitted record.
I'm using the powerapps edit form. But the problem goes deeper than just using the last submitted record. Most of the time multiple people will be using this app. So I need to use the sharepoint ID number since that won't ever be duplicated. Or were you trying to mean something else?
Hi @rowlinx
I am a bit lost on what you require. SharePoint will by definition create a new unique sequential ID for every new record created by anyone. The new ID is not created in PowerApps and it cannot be.
If you can be a little more specific then I can try to help.
In regards to the suggestion by @rlmckean, this can work but has a serious flaw. If someone else creates a new record after you have created yours but before the UpdateContext is called, then you will get their ID and not yours. That is why I suggested using the properties of the form, which avoids this pitfall. Please see here for details:
https://powerapps.microsoft.com/en-us/tutorials/control-form-detail/
In particular, please read the piece in relation to the LastSubmit property:
LastSubmit – The last successfully submitted record, including any server generated fields.
This property applies only to the Edit form control.
If the data source automatically generates or calculates any fields, such as an ID field with a unique number, the LastSubmit property will have this new value after SubmitForm successfully runs.
The value of this property is available in the OnSuccess formula.
Hi meneghino
Indeed I am lucky in that I have been working on an app that wont have too many users - However thanks for your warning which others need to consider.
The reason why I needed a work around was that I had imported data from webapps into sharepoint lists and I had a 'join' table that held IDs from the azure database. However when these were imported into sharepoint all the links broke as the IDs changed. I then had to create a table specific "oldid" column to access the old data and then needed to increment this for the new data.
@rwolinx would seem to want to create a unique Id number for her quotes or whatever.
Thanks for pointing us at the last submitted and onsuccess. - One really needs to dig deep to find this ! - I had read this tutorial but never got right to the bottom! - However no doubt there will be much trial and error as no example syntax is provided !!
Your solution using the clearcollect is good and demonstrates some coding I had not known about in the Patch routine
Catching the ID number is something that I have used for a long time in Access and WebApps - why has Microsoft hidden this away in Power Apps so it is so difficult to find ( like many other quirks it has ) !!
Cheers
Richard
Hi sorry that I wasn't clear originally.
I understand that sharepoint is the one that creates the ID number.
This is the process that I think would work
Enter data into first box --> autosave happens
Now that sharepoint has a saved entry an ID will have been created
Display ID + 170008
Essentially I want to use sharepoints ID system. But an ID is only created after a record is saved. I want the record to be auto saved right after someone enters data into the first box. This way I can show the proposal ID number that I calculated from the sharepoint ID number as the person continues creating the new entry.
Does that make more sense?
Hi @rowlinx, what you say is now clearer, thank you.
First of all a bit of background, apologies if this is clear to you already: SharePoint will only create a new ID when a new record is created. There is no way to 'ask' SharePoint what the new ID will be for a future new record or to reserve one.
Having considered this, are you absolutely sure that you want to create the new ID only with partial data in the new record?
I am asking this because normally a database would have conditions on columns (such as columns which require data etc., conditions on dates etc.) which are very good practice to keep data integrity. So if you create a partial record only to get its ID, then you need dummy data to make the partial record acceptable to the database. Also, please consider that if the app or the device or the user stops what they are doing then you are left with an incomplete record in the database.
If you are still convinced that you need a new ID before the record is completely created, then the easiest way is to have an action linked to a data input in the first box that creates and retrieves a new record. What shape this action takes depends on what the first control is (i.e. text input or drop down etc.) and if you are using a new item form. For example you could use an OnUpdate property of a control with a submit form action. The ID box could simply display ID+170008 by default.
Sorry I cannot be more specific, but hopefully I have given you some pointers.
Hi @Meneghino, thank you for your indepth reply.
I assumed that the best place to put this addition function was before the final record was saved. Since the SubmitForm function exits if it's successful.
Is there a workaround to the SubmitForm function. From my understanding on the OnSuccess property of the SubmitForm the Back() function is ran. However when I search properties I can't access the OnSuccess. I think if I could find a way to save the form without exiting I could get what I want out of this.
Thanks again
Hi @rowlinx
You should look at the LastSubmit property if you have not done so already. It may provide what you are looking for.
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 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
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