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

Moving records from one identical Sharepoint to another

Hello all, I have a relatively simple question. I have two Sharepoint lists that are identical, the idea is that once someone opts out of one list we save that record to another for record keeping and delete the original one. I have grabbed the record and put it into a variable and have confirmed it is the correct one. I have also successfully deleted the one one (Last line of code shown). But the second line is the problem, after I get the record, it does not show up in the second list. I have tried Defaults() as the second parameter but with no luck, I feel like I'm missing something obvious. I'd like to do this record move without a flow if possible.

 

Thanks!

 

 

Set(moveRecord, LookUp('WkShp Registration List', Email_x0020_Address.Email = VarUserEmail &&'Session ID'.Value = varParentItem.SessionID));

 

Patch('WkShp UnRegistration List', Defaults('WkShp UnRegistration List'), moveRecord);

 

Remove( 'WkShp Registration List', First(Filter( 'WkShp Registration List', Email_x0020_Address.Email = VarUserEmail && 'Session ID'.Value = varParentItem.SessionID)));

 

 

(again it's "onlyPatch('WkShp UnRegistration List', Defaults('WkShp UnRegistration List'), moveRecord);" that seems to be not working)

1 ACCEPTED SOLUTION

Accepted Solutions

Hey Warren, was given the ability to edit the Sharepoint, I couldn't delete the RegID or SessionID but I was able to remove everything else I didn't need. I have been putting everything in manually as I have all the info I need. I've gotten it down to this point, I'm not sure which is closer, but both of these don't add anything to the Sharepoint list. I assume that it has something to do with the ID being a lookup column? I have access to the number that corresponds to the lookup column on my current gallery, can I do anything with that?

/*
Patch(
'WkShp UnRegistration List',
Defaults('WkShp UnRegistration List'),
{
Full_x0020_Name: moveRecord.'Full Name',
Email_x0020_Address: moveRecord.Email_x0020_Address,
Organization_x002c__x0020_School: moveRecord.'Organization, School or Department',
Session_x0020_ID_x003a_Title: moveRecord.'Session ID:Title',
'Session ID': moveRecord.'Session ID',
RegID: moveRecord.RegID

},
moveRecord
);*/


Patch(
'WkShp UnRegistration List',
Defaults('WkShp UnRegistration List'),
{
'Full Name': moveRecord.'Full Name',
'Email Address': moveRecord.'Email Address',
'Organization, School or Department': moveRecord.'Organization, School or Department',
'Session ID:Title': moveRecord.'Session ID:Title',
'Session ID': moveRecord.'Session ID',
'RegID': moveRecord.'RegID'

}
);

 

Edit: I've since learned that RegID is auto generated and increments by one every record and that the SessionID Title is based on the session ID value. So I've commented those out

View solution in original post

22 REPLIES 22
WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @TheNewGuyAtWork ,

Have you looked at moveRecord (view > variables) to see what is in it? Also how many fields are in the record?

I have not, I see that is is a function in Powerapps, but I can't find info in the docs about it. There are 19 fields I believe, both Sharepoint's are identical. Also what are the arguments for the function? Nothing about moveRecord seems to come up when I google.

Anonymous
Not applicable

I'm not sure PowerApps will understand the Defaults() function in your second argument of Patch(). I've never actually used that method. I prefer to explicitly rebuild my record when patching from one table into another. So, in your case, I'd try this...

Patch(
    'WkShp UnRegistration List',
    {
        Email_x0020_Address: moveRecord.Email_x0020_Address,
        Session_ID: moveRecord.Session_ID
    },
    moveRecord
)

If that record already exists in the WkShp UnRegistration List, then it will be replaced with moveRecord. If it doesn't exist, then a new record will be created with the information in moveRecord.

 

At least, that's how I understand it should work. I actually abandoned SharePoint lists a while ago for use with PowerApps, because they were a real pain to work with. Instead, I set up SharePoint libraries that store all the information I would have used in lists with a combination of JSON files and folder structure.

This helps a lot, I think I've just about got it, this is what I have:

Patch(
'WkShp UnRegistration List',
{
Email_x0020_Address: moveRecord.Email_x0020_Address.Email,
Session_x0020_ID_x003a_Title : moveRecord.'Session ID:Title'.Value
},
moveRecord
);

 

Some of the info I needed is in complex field types, so the email is actually in moveRecord.Email_x0020_Address.Email. I ran into something similar when doing a collection but I'm still unsure how to lay it out based on that. The error is "The type of this argument  Email_x0020_Address does not match the expected type "Record" Found Type "Text" and "the patch function has invalid arguments". The thing is if I give it a record it's a complex field type and won't get the data it needs

 

There is actually a lot of fields in the table I'm trying to place this into, but these are really the main two I need.

That error makes sense, because the field Email_x0020_Address in SharePoint is an object (you can tell, because it has a set of properties associated with it), and you're trying to put a text value (Email_x0020_Address.Email) into it. Instead, try identifying the record using the entire email address object.

Email_x0020_Address: moveRecord.Email_x0020_Address

Another option is to compare the Email property of each object (both text values).

Email_x0020_Address.Email: moveRecord.Email_x0020_Address.Email


'WkShp UnRegistration List',
{
Email_x0020_Address: moveRecord.Email_x0020_Address,
Session_x0020_ID_x003a_Title : moveRecord.'Session ID:Title'
},
moveRecord
);

 

 

I tried to just pass in the records, this code works but upon checking the Sharepoint list no records appear when I use the button to submit. When using both with .Email and .Value respectively they produce an error. I'm not sure why it wouldn't error but not put anything into the list.

After reading through the doc for the Patch() function, it looks like you really are supposed to use the Defaults() function as the second argument to create a new record—I've never done it that way, but I guess that's the official way to do it. So, your original expression should have worked.

 

I wonder if there is some really obscure difference between the lists. Did you create the WkShp UnRegistration List using SharePoint's "create from another list" functionality? If not, you'd have to go through all the list settings with a fine-toothed comb to make sure everything's identical.

Screenshot 2021-04-09 155513.png

 

Another possible solution might be to create the new record not using a copy of the original, but only using those fields which are present in the original record. That is...

Patch(
    'WkShp UnRegistration List',
    Defaults('Wk UnRegistration List'),
    {
        Email_x0020_Address: moveRecord.Email_x0020_Address,
        Field2: Value2,
        Field3: Value3,
        etc...
    }
)

 This would essentially force SharePoint to create the new record using defaults, and then replace only those fields you specify (which would be everything in moveRecord, if you list them all). Just make sure all your data types match between record values.

Anonymous
Not applicable

Just thought of something. If the SharePoint list field ID is contained in your moveRecord record, then that might also be why it's failing when you try to pass the entire record in the third argument. You can't explicitly set the ID field, since that's unique and auto-generated in all SharePoint lists.

I have a feeling this is the actual issue, honestly is there a way to disregard that one field? Or at least set it to auto generate?

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