cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
grodinsm
Helper I
Helper I

Create a second record entry from gallery

I've got my app now working very nicely, however I've now been asked to be able to create a "copy" of the record. I've built a form to collect information about someone during a meeting. The users now want to be able to click a button in the gallery next to that person's name and create a second record entry, so that when they have a second meeting with the person, they're not editing the original entry. 

 

I have no idea where to start and am looking for help!

 

I need all of the information to be copied over, as if we're just editing the same record, but any changes are saved under a new recordID. When this happens, I want to edit a hidden column in my database called "Current" so that I can tell the rest of our systems which copy is the most current. 

 

All of my saves right now are being done using the SubmitForm function, I'm not using patch. and am using SQL. Looking for the least intrusive way to do this since it's all working perfectly right now. 

1 ACCEPTED SOLUTION

Accepted Solutions

That did the trick!! I was about to reply and say it had reverted back to displaying the original entry again, but realized I had put the closing bracket for the SET in the wrong place. 

 

Here is the final code for anyone who is in a similar situation:

 

UpdateContext({ResetVar: true}); 
UpdateContext({ResetVar: false});
 Set(rnew,Patch('[dbo].[Intake_form]',Defaults('[dbo].[Intake_form]'),
{First_Name:ThisItem.First_Name}));
Set(IDVar,rnew.Form_Number);
ClearCollect(updcoll, DropColumns(Collect (upd2,ThisItem),"Form_Number"));
Set(rnew,Patch('[dbo].[Intake_form]',{Form_Number:IDVar},First(updcoll))); Patch('[dbo].[Intake_form]',ThisItem,{Current:"N"});
EditForm(Form1); 
Navigate(Screen1, ScreenTransition.None,{displayitem:rnew})

And then on the form1 screen, change the Items property to "displayitem"

 

Thank you very much @BitLord69, couldn't have done this without your help. 

View solution in original post

15 REPLIES 15
v-monli-msft
Community Support
Community Support

Hi @grodinsm,

 

My understanding is that you have already created an app using one SQL tableA. Now you need another editform that will update the record to another different tableB. But you want to copy the data from tableA to tableB. If this is the situation, I'm afaid  that this cannot be achieved so far. One form can only have one data source binded. And if you want to have the data from tableA, you have to use it as the data source in form. So that you cannot update this form also to tableB.

 

You will have to manually update the record for tableB with the same data.

 

Maybe you could also add an idea in the PowerApps Ideas forum, so it might be considered for future releases.

https://powerusers.microsoft.com/t5/PowerApps-Ideas/idb-p/PowerAppsIdeas

 

Regards,

Mona Li

Community Support Team _ Mona Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Here are my thoughts on your problem:

 

The best way is probably to split the information up in two different tables, so you will have one table with the information about each person that will not change very often, and then you have a related table with an entry for each meeting. That way you can have two galleries: one with each person, and then a sub-gallery that will show all entries for the selected person.

 

If you do not want to go down that road, you can use Patch to create a copy of the selected person. In the onSelect of the Create Copy-button in the gallery you do a call to Patch, that will look something like this:

 

 

Patch(TableName, Defaults(TableName), {Column1:GalleryName.Selected.Column1, Column2:GalleryName.Selected.Column2....})

 

 

Obviously you have to change the names, otherwise it should work like a charm, I use it in a couple of places in my apps.

 

Read more about Patch here: https://docs.microsoft.com/en-us/powerapps/functions/function-patch

 

Good luck, and don't be afraid to ask again if something is unclear or you need more help!

@v-monli-msft Sorry if that was unclear. my SQL table has an autonumber column as the primary key called "Form_number". lets say I have someone, "John Smith" as Form_Number="135" I'd want to have a new entry in the same table (say, #136 if that's the next available number) with all of the same information #135 has. 

 

When using the "New" function in my app, it grabs the next available Form_number automatically.  

 

@BitLord69, I will try your suggestion today and see if that works. Do i have to type in every single column name, or is there a way to patch all columns? I have over 100 fields in my form. 

Good morning!

 

That's a really good question! I'm not sure.

 

Are all the 100 columns relevant for each meeting, or for the person and then stays the same for every meeting? If it's the second case, then you should really think about splitting the information into two tables so you don't have so much duplicate data. If it's the first case, do ALL the data need to be copied, or can you just copy a subset, the most pertinent information?

 

Here's part of what the documentation says:

Patch( DataSource, BaseRecord, ChangeRecord1 [, ChangeRecord2, … ])

  • DataSource – Required. The data source that contains the record that you want to modify or will contain the record that you want to create.
  • BaseRecord – Required. The record to modify or create. If the record came from a data source, the record is found and modified. If the result of Defaults is used, a record is created.
  • ChangeRecord(s) – Required. One or more records that contain properties to modify in the BaseRecord. Change records are processed in order from the beginning of the argument list to the end, with later property values overriding earlier ones.

I wonder if it's possible to first create the record with Patch and save the result in a local variable, and then use a second call to Patch with the newly created record as base record and the record you want to make a copy of as ChangeRecord.

 

Not sure what the syntax have to be, but play around with this general idea:

UpdateContext({rNew:Patch(TableName, Defaults(TableName), {Column1:GalleryName.Selected.Column1})});Patch(TableName, rNew, {PrimaryKeyColumn:GalleryName.Selected.PrimaryKeyColumn})

 

It's especially the last part in italics I'm unsure about, so go play around and see if you can get it to work.

 

Good luck!

 

To answer your first question, I need a full copy of all data. the idea is that any of it COULD be edited in the second meeting, but we want to know exactly what it looked like during the first meeting, and just make adjustments in the second meeting. We're using them as a snapshot in time. 

 

I tried what you suggested, pretty much using the code you wrote. I have a second record in my database, the first patch I only asked it to copy the person's first name, and that worked. when I get to the second patch, it looks like this: 

 

Patch('[dbo].[Intake_form]',rnew, ThisItem)

 

I can tell Powerapps really is trying to do exactly what I want here, by copying ALL columns... unfortunately it's also trying to copy the Primary Key column "Form_Number", so i get this error: "Form Number: The specified column is read only and can not be edited." 

if I could tell it "ThisItem EXCEPT for Form_Number" it would work perfectly. or even if I could say something like  "this Item columns(2:100)" based on column index... 

 

So it looks like patching data one by one by typing out each column name works (since First Name worked fine) but since the primary key is autogenerated in the database a copy-all isn't working. 

 

Any further thoughts?

Update:

 

I've figured out the code to get the record duplicated. After the post I wrote above, I discovered the dropcolumn function. (working code posted below). I have a new issue though. I can't figure out how to get the form to load the new record. Any attempts to push the new record through as part of the Navigate function doesn't make a difference, because the form on the edit screen calls for Items="TemplateGalleryList1.Selected"

 

I'm not sure whether to re-write the Items code, or force the gallery to re-collect it's items to include the new record, and then somehow re-point "selected" to the new record.

 

Here's the code that works, the database gets a second record with everything other than "Form_Number" duplicated. But as I said the EditForm screen pulls up and edits the original record.

UpdateContext({ResetVar: true});
UpdateContext({ResetVar: false});
 Set(rnew,Patch('[dbo].[Intake_form]',Defaults('[dbo].[Intake_form]'),
{First_Name:ThisItem.First_Name}));Set(IDVar,rnew.Form_Number);
ClearCollect(updcoll, DropColumns(Collect (upd2,ThisItem),"Form_Number"));
Patch('[dbo].[Intake_form]',{Form_Number:IDVar},First(updcoll)); Patch('[dbo].[Intake_form]',ThisItem,{Current:"N"});
EditForm(Form1);
Navigate(Screen1, ScreenTransition.None,{displayitem:Filter(Collection1,Form_Number=IDVar)})

Good morning!

 

Seems you've come along way already, great job!

 

Since you are already passing the record to edit in the call to Navigate, you can use the variable displayItem in the edit screen's Item-property. One question though: isn't that the same as rnew? Just pass that variable in the Navigate (dispalyitem:rnew), or use it directly (since you use Set to set its value).

 

 The gallery should repopulate its list automatically, but I don't know how to force it to select a particular row.

 

Good luck!

I just tried that, didn't work, it still pulled up the original record. i used displayitem:rnew but I believe the problem is on the form screen, not on the gallery screen. it still knows that my duplicate button was attached to "TemplateGalleryList1.Selected" which is in the items field of Form1. 

 

either I have to redirect the "selected" piece, or I need a new code for the Items box. I've tried a few combinations but haven't found something that works. 

 

Hi again,

 

As I wrote in my last reply: Since you are already passing the record to edit in the call to Navigate, you can use the variable displayItem in the edit screen's Item-property. 

 

As you write yourself, you have to change the form's Item-property, and you can do it as above. If I understand it correctly, the form is on Screen 1, right? So, Form1:Item = displayitem; that should do the trick. You just have to remember to set the variable displayitem in all the places where you call on the form.

 

If oyu need any further help, can you post a (few) screen shot(s) of your app? It's easier to see how it all comes together that way.

 

Good luck!

Helpful resources

Announcements

Super User of the Month | Drew Poggemann

As part of a new monthly feature in the Community, we are excited to share that Drew Poggemann is our featured Super User for the month of February 2024. If you've been in the Community for a while, we're sure Drew's name is familiar to you, as he is one of our most active contributors--he's been a Super User for five consecutive seasons!   Since authoring his first reply 5 years ago to his 514th solution authored, Drew has helped countless Community members with his insights and expertise. In addition to being a Super User, Drew is also a User Group leader and a Microsoft MVP. His contributions to our Super User sessions and to the new SUIT program are always welcome--as well as his sense of humor and fun-loving way of sharing what he knows with others.   When Drew is not solving problems and authoring solutions, he's busy overseeing the Solution Architecture team at HBS, specializing in application architecture and business solution strategy--something he's been doing for over 30 years. We are grateful for Drew and the amazing way he has used his talent and skills to help so many others in the Community. If you are part of the SUIT program, you got to hear some great tips from Drew at the first SUIT session--and we know he still has much more to share!You can find him in the Community and on LinkedIn. Thank you for all you do, Drew!

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Our team will be reviewing posts using the new "Copilot Studio" label to ensure we highlight and amplify the most relevant and recent content, so you're assured of high-quality content every time you visit. If you share a post that gets featured in the curated gallery, you'll get a PM in the Community to let you know!The curated gallery is ready for you to experience now, so visit the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community. We can't wait to see what you "cook" up!      

Celebrating a New Season of Super Users with Charles Lamanna, CVP Microsoft Business Applications

February 8 was the kickoff to the 2024 Season One Super User program for Power Platform Communities, and we are thrilled to welcome back so many returning Super Users--as well as so many brand new Super Users who started their journey last fall. Our Community Super Users are the true heroes, answering questions, providing solutions, filtering spam, and so much more. The impact they make on the Communities each day is significant, and we wanted to do something special to welcome them at our first kickoff meeting of the year.   Charles Lamanna, Microsoft CVP of Business Applications, has stressed frequently how valuable our Community is to the growth and potential of Power Platform, and we are honored to share this message from him to our 2024 Season One Super Users--as well as anyone who might be interested in joining this elite group of Community members.     If you want to know more about Super Users, check out these posts for more information today:    Power Apps: What is A Super User? - Power Platform CommunityPower Automate: What is A Super User? - Power Platform Community Copilot Studio: What is A Super User? - Power Platform Community Power Pages: What is A Super User? - Power Platform Community

February 2024 User Group Update: Welcoming New Groups and Highlighting Upcoming Events

It's a new month and a brand-new year, which means another opportunity to celebrate our amazing User Groups!Each month, we highlight the new User Groups that have joined the community. It's been a busy season for new groups, because we are thrilled to welcome 15 New User Groups! Take a look at the list below, shared by the different community categories. If your group is listed here, give this post a kudo so we can celebrate with you!   We love our User Groups and the difference they make in the lives of our Community! Thank you to all the new User Groups, new User Group leaders--we look forward to hearing about your successes and the impact you will leave!   In addition to our monthly New User Group spotlight, it's a great time to share some of the latest events happening in our User Group community! Take a look at the list below to find one that fits your schedule and need! There's a great combination of in-person and virtual events to choose from. It's a great time of year to connect and engage with User Groups both locally and online. Please Welcome Our NEW User Groups   Power Platform: Heathcare Power Platform User Group Power Platform Connect Hub Power Platform Usergroup Denmark Mexico Norte- Power Platform User Group Pune Power User Group Sudbury Power Platform User GroupMicrosoft User Group GhanaMPPBLR - Microsoft Power Platform Bengaluru User Group Power Apps:   Myrtle Beach Power Platform User GroupAnanseTechWB PowerApps Copilot Studio: Pathfinders Power Platform Community Dynamics365: Cairo, Egypt MSD 365 Business Central/NAV/F&O User GruopMS Dynamics 365 Business Central LatamCincinnati OH D365 F&O User Group February User Group Events February 2024 Cleveland Power Platform User GroupPortallunsj - Februar 2024Indiana D365/AX February User Group MeetingQ1 2024 KC Power Platform and Dynamics 365 CRM Users Group 

Super Users 2024 Season One is Here!

   We are excited to announce the first season of our 2024 Super Users is here! Our kickoff to the new year welcomes many returning Super Users and several new faces, and it's always exciting to see the impact these incredible individuals will have on the Community in 2024! We are so grateful for the daily difference they make in the Community already and know they will keep staying engaged and excited for all that will happen this year.   How to Spot a Super User in the Community:Have you ever written a post or asked for help in the Community and had it answered by a user with the Super User icon next to their name? It means you have found the actual, real-life superheroes of the Power Platform Community! Super Users are our heroes because of the way they consistently make a difference in the Community. Our amazing Super Users help keep the Community a safe place by flagging spam and letting the Community Managers know about issues. They also make the Community a great place to find answers, because they are often the first to offer solutions and get clarity on questions. Finally, Super Users share valuable insights on ways to keep the Community growing, engaging, and looking ahead!We are honored to reveal the new badges for this season of Super Users! Congratulations to all the new and returning Super Users!     To better answer the question "What is a Super User?" please check out this article: Power Apps: What is A Super User? - Power Platform CommunityPower Automate: What is A Super User? - Power Platform Community Copilot Studio: What is A Super User? - Power Platform Community Power Pages: What is A Super User? - Power Platform Community

Did You Attend the Microsoft Power Platform Conference in 2022 or 2023? Claim Your Badge Today!

If you were one of the thousands of people who joined us at the first #MPPC Microsoft Power Platform Conference in 2022 in Orlando--or attended the second-annual conference in Las Vegas in 2023--we are excited to honor you with a special community badge! Show your support for #MPPC Microsoft Power Platform Conference this year by claiming your badge!         Just follow this link to claim your badge for attending #MPPC in 2022 and/or 2023: MPPCBadgeRequest    Want to earn your badge for 2024? Just keep watching our News & Announcements for the latest updates on #MPPC24.

Top Solution Authors
Top Kudoed Authors
Users online (3,004)