Hi there all - Hope everyone is ok.
I'm new to PowerApps but trying to pick it up as quick as possible.
In the app I'm creating, I'm using a Sharepoint list as the data source and destination of data writeback when submission is made form the app.
However as part of that process, for every entry that is submitted via the app to the SP List, I use the SP ID column as the entry's unique reference.
There is a process we have by which users should be able to submit amendments to the entry's made previously, but without changing any of the data deposited in the first submission. The way I've got around this is by having a combo box field that is visible depending on the selected option in field 1 (New Submission or Amendment). If the user picks amendment, an additional field called 'Amended Reference Number' appears.
This is where my issues begin -
The selectable options in the Amendment Reference Number Combo Box field, I want to automatically reference back to the ID column in SP. This is so that the user can select their previous submission ID. Then anyone reviewing the data for audit or any other purpose would know that the entry made was an amendment to previous entry ID#65. Once the user clicks submit, although the Amended Reference Field in the PowerApp is displaying the ID column entries, it writes that data back the submit form data for that field to the SP column of Amended Reference # not the ID column in SP.
Is anyone able to help me with the right coding to use here as fr the life of me I can't find the answer... And I've sat through a number of Shane Young's videos on YouTube (They are great) but have not been able to find an answer.
Thanks
Dean
@Deano12 this is a little hard to visualise, can you share some code & maybe screenshots to help? Also, it sounds like you need a Patch() [create new SP item] as well as a UpdateIf() OR Patch() [update an existing SP item]. Are you doing both?
As I said code & screenshots would help us help you
Hi there - Thank you for your reply,
Here are some screenshots of the app as it stands today:
HomeScreen>NewEntryScreen>HistoricalEntryScreen>DetailsScreen:
I hope you are able to see where I'm going with this - I need the Amended reference field to only search the Entry # field that is shown on the detail screen, as they shouldn't be able to make up a number if they are referencing a previous entry?
The current code in the Amending entry field is:
ThisItem.'Amended Reference'
I'm not sure what the formula is for it to reference a different field even though then the user submits the form, it needs to patch the data back into an Amended Reference column on Sharepoint.
Here are the columns from SharePoint:
Hope this helps
Thanks
@Deano12 It sounds like when someone makes an amendment they are 'Editing an item' in SP, is this correct? If so, you are probably best adding an EDIT icon on your DOB Entry screen, similar to the screens used if you let PA make a basic app for you.
the standard 'create an app' setup has these screens:
Browse Gallery --> Display Form --> Edit/New Form
The equivalent screens in your app are:
Previous Entries --> DOB Entry --> DOB Data Entry
so you'd just follow the standard app design / code but add in the edit function. This way, the person making an amendment would be editing the correct ID.
This would only do one at a time but you mention a combobox so maybe you want to amendment more than one item each time? If that was the case you would need to add a bit more functionality whereby you add each item (picked using the combo box IDs) to a collection then when done the collection- not the form - is patched back to SP. It's a little involved but doable.
hope this helps - let me know if I've understood your situation correctly as well, I could be totally off?
Hello again. And once again, thank you for your reply.
In a normal situation, you would be correct and I've already presented that option to the stakeholders for this solution. However, the paper-based document that this is to replace comes with some compliance restrictions behind it.
What I am replacing is a Daily Occurrence Book. Users fill in one row of the document and move on.
However, whatever entry they add needs to stay there without change. If they were to make a mistake or update a situation, a new line needs to be added with a reference back to the original entry on the document. This is so that an auditor/manager can look back and see what was first recorded compared to what is now being stated as fact.
It's the new entry relating back to the old entry that I struggling to digitize. I need the Amending Previous Entry Number field on the app to show the exact Entry numbers that have been submitted so far so that they can not put in a random number and it not mean anything while submitting that information back to the SharePoint document in another column. This means that when someone looks at the recorded data, they can see that the entry is related to Entry ID # 1 for example, rather than actually changing Entry # 1.
I hope this helps explain the desired function of the app a little more.
I've been playing some more and managed to get the drop down populated by the Entry #'s logged before it, however, when I try to submit the data, I get an error that the data is invalid for input. yet the SharePoint column that it should be pushing it back to is a Single Line of Text column type?
The code so far on the EditForm is:
The section names for that particular part of the form are:
To be honest - After I'm able to crack this step, the next step is to filter the Gallery and all 'Referencing' fields, based on a separate SP List that states.
User, Jack belongs to Site Code S1, therefore all data to be displayed for selection/view should only be S1 data. I'm not looking forward to that bit, as I've not used the User.() function before.
But first I need to get over the Amended Entry Number problem first.
Thanks.
Sounds to me like you are nearly there. Try changing the SP column's type to a number. I did something similar recently and that's how I set it up and it's working fine.
You will need to refresh your datasource inside your app and changing the type may not adjust the relevant DataCard type, not sure? PAs may be smart enough to correct this for you though?
For the User() I use something similar in an app of mine where I get the users FullName and Email and send data to a SP list for Login/Logout dates & times. The code on my Login button includes :
(Note: to make this work get the Office365Users connector)
Set(varLoggedInUser, User() ) ;
Then using the above variable I get Full Name and Email via:
varLoggedInUser.FullName
varLoggedInUser.Email
You can then use these throughout your app as needed.
Sorry, I was talking about adjusting the Amended Reference column type. Yes you are correct, you cannot adjust the type of the ID column. I've assumed the Amended Reference column stores the ID from the original item only, is that correct?
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