Moving records from one identical Sharepoint to another

[TheNewGuyAtWork]

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)

[Anonymous]

It will auto-generate in the new list, anyway (and it won't be the same as the ID in the other list). The only way to avoid it would be to explicitly list the other (settable) fields explicitly in the third argument. As I said earlier, I've never tried creating a new list item by passing the entire record from another list, so I don't even know if you can do it that way. You might need to always explicitly name fields in that third argument so as to avoid things like the ID field.

[TheNewGuyAtWork]

I don't need to specifically avoid it, I really just need those two things to appear in in another list, the rest is take it or leave it, I'll try to make a list with just a few fields and remove the old ID column and post again if that gets me anywhere

[WarrenBelz]

@TheNewGuyAtWork ,

Back in my time zone now - @Anonymous is getting close and is correct in you can do it with the fields you want to change. You could also try dropping the ID as mentioned

With(
   {
      move_record
      DropColumns(
         moveRecord,
         "ID"
      ),
   },
   Patch(
      'WkShp UnRegistration List',
      Defaults('WkShp UnRegistration List'),
      move_Record
   )
)

but I have never found this syntax you are using (Patching a matching record and hoping Power Apps/SharePoint works it all out) reliable, but this should work

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

 You would then add any other fields you want to save in the new record.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

[TheNewGuyAtWork]

Hey Warren, thanks for helping out again, I used the code you had first as it sounds like it'll be a better fit, although it looks like their might be a syntax error? I can't seem to find it, all I've done is change the session ID to be the correct name, patch by itself seems to be picked up fine. 

Edit: Also do I need to do anything special because Session ID is a complex field? 

[WarrenBelz]

@TheNewGuyAtWork ,

Is it a Choice Field (not a Lookup) - if so

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

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

[TheNewGuyAtWork]

Okay I think I see, I'll worry about the complex fields when I can get it to stop giving me errors, it doesn't like the way with was used and expects a colon (see last image if you haven't) Until then, I'll keep playing with it.

Edit: Also after looking at With() I'm not even sure that's what I need it looks like it evaluates several thing, I just need the single record I have in a variable into another list, I'm starting to second guess if I'm on the right track

[WarrenBelz]

@TheNewGuyAtWork ,

As I mentioned, I have never found it reliable - I just supplied some code that gets rid of the ID before you try to Patch the rest.
As for complex field types - it is better you forget them entirely - I have a blog on this if it assists.

If that is a LookUp column you are trying to Patch, you need this

Patch(
   'WkShp UnRegistration List',
   Defaults('WkShp UnRegistration List'),
   {
      Email_x0020_Address: moveRecord.Email_x0020_Address,
      Session_ID: 
      {
         Value:moveRecord.Session_ID.Value
         Id:moveRecord.Session_ID.Id
      },
      NextField:moveRecord.NextField
      . . . . . . .
    }
)

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

[TheNewGuyAtWork]

Okay I see! Think something just clicked and I think I see how the formatting is supposed to go, I imagine that if "Session ID", or "Session_x0020_ID" has like its own set of 6 or so fields I would need to manually specify those too as well correct? I think I might have to get a new Sharepoint list going that doesn't have like 19 columns so that I can make it so I only have to copy over the important data.

[WarrenBelz]

@TheNewGuyAtWork ,

Is Session ID Managed Metadata - if so, get rid of it as this serves no real purpose I can think of.

As per the blog, unless you have a pressing need to do something (very) different, keep to simple field types - you will find your Power Apps journey much smoother.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

[TheNewGuyAtWork]

I'm not sure what the formal name is in Sharepoint/Powerapps because I'm super new, but it's essentially a link to a primary key of another table, meaning when you click on it it's info for the session itself. Those all being attributes that cannot be change like the title and other info.  Which is where Session ID: title is generated from I believe