cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

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

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 (967)