Power Apps Patch/coding help. PLEASE - URGENT - TIME SENSITIVE!

[axray]

Hi all,

I am self-taught in Power Apps and I know I'm in over my head with this issue, but the project needs to be completed and rolled out ASAP. Please, be as detailed as possible... I just need to complete this as quickly as I can.

So. I started with a SharePoint list and a customized Power Apps Edit Form. Unfortunately, the list has a TON of lookup type fields (mostly people picker and date fields)... and it's on SharePoint Online, which has a max of 12 lookup fields (in a view, yes, but also to submit my Power Apps form).

So then I thought I could figure out how to use the Patch function and use combo boxes and text fields... but I can only find bits and pieces of coding for this online, so I'm not sure what I'm doing... 

I then created a Canvas app with a vertical gallery and an Edit Form to the right of it. But again, I don't know how to code it to write the combo boxes/people pickers to the text columns in my SharePoint list. I have never built a Canvas app before, but I've watched a ton of videos, so I have it mostly set up. I've seen a lot of things about Collections, but I've never done that, either, so I'm not sure if I need to try something like that?

Can someone please let me know the best solution here to circumvent the lookup type threshold/max/limit? Also, please provide all necessary coding for combo boxes/people pickers/Patch, etc.?

Thank you so much! 

----------------------------------

UPDATED WITH MORE SPECIFIC QUESTIONS AND A SCREENSHOT OF APP:

So, I have a TON of information I've gathered from YouTube videos (Reza, Shane, April, Darren, etc) - now I just need help piecing it together... 

I have included a screenshot of my gallery on the left/edit form on the right. What I basically need an answer to is this:

Do I only write Patch coding for the combo boxes/people picker and date picker fields that I added to compensate for the inability to use additional lookup type fields? Will all the other SharePoint column fields just work as normal, with no additional coding? 

Do I still include Defaults coding in the Patch, for when it's a new ticket vs an updated/edited ticket? If so, what should that coding look like? Do I wrap it in an If statement somehow? If so, what should that look like? If not, what should I do instead? New button vs Update button with separate coding? If so, what if the user accidentally hits the wrong button?

I have bits and pieces of code and I have a general idea of what needs to be done... I just don't have the big picture/finished coding image yet.

Any help would be super appreciated! Thank you!

[axray]

Anyone? Pretty please?

[jlk1]

You could try using flows to auto update the list. So on your powerapp, you would just create a dropdown of all of the people to choose from or just use a text input. Then in power automate you do

When an Item is Created->Get Item->Search for Users->Update item

Ex. 

This worked for me to essentially patch lookup columns in lists, its nice because the search for users will autofill to the person with the closest spelling so you can type first or last name and it should still work. Only downside is that it can only be used when an item is created (setting it to modified creates an infinite loop) and you have to wait the few minutes for the list to be updated

[axray]

Thanks - I have a ton of lookup type columns (fields) and I need them all to write to SharePoint alongside the existing SharePoint columns (12 lookup and all the non-lookup columns)... for new tickets and to update existing tickets. I feel like it probably isn't as complicated as I think it is, but I just don't know enough to know for sure...

[axray]

Hmmm.... what if I tried asking more specific questions?

So, I have a TON of information I've gathered from YouTube videos (Reza, Shane, April, Darren, etc) - now I just need help piecing it together... 

I have included a screenshot of my gallery on the left/edit form on the right. What I basically need an answer to is this:

Do I only write Patch coding for the combo boxes/people picker and date picker fields that I added to compensate for the inability to use additional lookup type fields? Will all the other SharePoint column fields just work as normal, with no additional coding? 

Do I still include Defaults coding in the Patch, for when it's a new ticket vs an updated/edited ticket? If so, what should that coding look like? Do I wrap it in an If statement somehow? If so, what should that look like? If not, what should I do instead? New button vs Update button with separate coding? If so, what if the user accidentally hits the wrong button?

I have bits and pieces of code and I have a general idea of what needs to be done... I just don't have the big picture/finished coding image yet.

Any help would be super appreciated! Thank you!