Hi I had a dropdown in my PowerApps Form (PowerApps form linked to a SharePoint Online List in back end) and I want the value/s autopopulated via URL params. It seems so easy after following various guides and this one gave me my solution, https://powerusers.microsoft.com/t5/General-Discussion/I-simply-want-to-open-a-Powerapps-form-pre-populated-with-a/m-p/93272#M34954 however that was yesterday and I can't seem to get it working now.
Steps to reproduce issues/follow tut to make work from beginning:
- Create a param url e.g: https://web.powerapps.com/apps/1d172172-6789012345?h_s_id=6
- I save that link somewhere in SharePoint - in page, list wherever
- In the PowerApps form I click on the form and move it to first position i.e. so my form loads first AND NOT the default first screen which is normally BrowserScreen1
- I click on the whole form screen's (not the default first screen which is normally BrowserScreen1) onStart function I add: Set(RecordLookup,Param("h_s_id")) and then in the form's dropdown Item's field I added LookUp('HandS Test 1.0', ID=RecordLookup)
Now it should then work by simply clicking on the link from within SharePoint and the dropdown autopopulated based on the ID. I obviously expect back the dropdown to have selected Golf since my param in URL is set to 6 i.e. Golf's ID in the list.
My SharePoint List is as follows and I've included the API return for clarity: Sharepoint list:
Title |Event | Reason
=== | === | ===
test1 |Golf | Warm
test2 |Pool | Fun
`<d:Id m:type="Edm.Int32">6</d:Id> <d:Title>test1</d:Title> <d:Event>Golf</d:Event> <d:Reasons= m:null="true" />Warm<Reasons> <d:Id m:type="Edm.Int32">7</d:Id> <d:Title>test2</d:Title> <d:Event>Pool</d:Event> <d:Reasons= m:null="true" />Fun<Reasons>`
Is my issue that the form (EditScreen1) doesn't have a onStart functionality and feature?? The best I can recall when it did work yesterday it was just before switching orders of the screens. But now really puzzled.... :-//zz
UPDATE: Also just to add I have tried rolling back using the versions tool from within settings of PowerApps but still not working and PowerApps versions did stick so can't blame MS, well not yet anyways... :-)