cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
AntwainPatrick
Level: Powered On

Power App before Sharepoint?....Cart before the horse?

I have a PowerApp with Dropdown boxes, Choice boxes and Date pickers all in one form.  Is it possible to put the cart before the horse and have all my selections write back to a Sharepoint List?  I'd hate to find out I have to go back to the very beginning and create Sharepoint list, then PowerApp.

 

Thanks for your HELP.

1 ACCEPTED SOLUTION

Accepted Solutions
Merlijn
Level 8

Re: Power App before Sharepoint?....Cart before the horse?

Like Reza said, you need to 'patch'. I always use patch because it gives you the freedom of designing a user interfaces and update fields that the user doesn't even see based on like variables.

You need to connect to the SharePoint list.

Patch:
Patch(source,record,{fieldname:fieldinput,fieldname:fieldinput})

When a new record:
Patch(source,defaults(source),{fieldname:fieldinput,fieldname:fieldinput})

When editing a record you need to look up for a unique record.
Patch(source,lookup(source;ID=Gallery.selected.id,{fieldname:fieldinput,fieldname:fieldinput})

Hope this helps.

You can also patch data that's not visible on the app. Like a user field you can patch with the username user().fullname.

Good luck and have fun!

View solution in original post

2 REPLIES 2
Dual Super User
Dual Super User

Re: Power App before Sharepoint?....Cart before the horse?

Hi @AntwainPatrick ,

 

You would have to use the Patch statement to write the data to SharePoint once your form is ready to post data to SharePoint

 

If you start with the horse 🙂 then you would have the options of directly using the SharePoint form using the PowerApps form control

 

Regards,

Reza Dorrani

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

Merlijn
Level 8

Re: Power App before Sharepoint?....Cart before the horse?

Like Reza said, you need to 'patch'. I always use patch because it gives you the freedom of designing a user interfaces and update fields that the user doesn't even see based on like variables.

You need to connect to the SharePoint list.

Patch:
Patch(source,record,{fieldname:fieldinput,fieldname:fieldinput})

When a new record:
Patch(source,defaults(source),{fieldname:fieldinput,fieldname:fieldinput})

When editing a record you need to look up for a unique record.
Patch(source,lookup(source;ID=Gallery.selected.id,{fieldname:fieldinput,fieldname:fieldinput})

Hope this helps.

You can also patch data that's not visible on the app. Like a user field you can patch with the username user().fullname.

Good luck and have fun!

View solution in original post

Helpful resources

Announcements
Better Together’ Contest Finalists Announced!

'Better Together’ Contest Finalists Announced!

Congrats to the finalists of our ‘Better Together’-themed T-shirt design contest! Click for the top entries.

thirdimage

Power Apps Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

sixthImage

Join THE global Microsoft Power Platform event series

Attend for two days of expert-led learning and innovation on topics like AI and Analytics, powered by Dynamic Communities

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

thirdimage

Community Summit North America

Innovate, Collaborate, Grow - The top training and networking event across the globe for Microsoft Business Applications

Top Solution Authors
Top Kudoed Authors
Users online (8,694)