Forum Discussion
Creating a button that makes a choice On Click
Hi Ibendlin
Thanks for your guidance,
I used the below code to make the switch work -
If(IsBlankOrError(LookUp('ACTION_&_COMMENT_LIST2',ThisItem.ROW_ID="")), Navigate(IssueUpdateForm ),Navigate(CreateRecordForm))The strange thing that i have been struggling with is getting the order of the argument, i thought Navigate(CreateRecordForm should go before Navigate(IssueUpdateFormand using the ROW_ID="" i had been trying to use 0ThanksCarl
Hi Ibendlin
Just to clarify
1) Yes i select the row which selects the Invoice Number,
a) If there is no record on my Sharepoint List Comments box is blank, which is the expected result.
b) If there is a record on the Sharepoint list it retrieves the Comment, which is the expected result
2) Rather than have 2 buttons,
a) one which takes you to "Update Form" where you can edit the details on the form
b) The other takes you to "Create Form" (Via Patch) to create a new row record
I would like to have one button which recognizes if a row record exists or doesnt exist and takes the user to the correct form, "Update Form" or "Create Form"
Why have two forms? how are they different?
I thought thats how you did it,
When updating a row record use Update Form (to avoid duplication of row records)
When creating a row record use Create From via Patch
You would make that decision in PowerApp. When you get the single value from Power BI, try to match it to your collection. Show the edit form if you have a match, the create form otherwise. Upon patching use the ID for edit and default for add.
Hi Ibendlin
Thanks for your guidance,
I used the below code to make the switch work -
If(IsBlankOrError(LookUp('ACTION_&_COMMENT_LIST2',ThisItem.ROW_ID="")), Navigate(IssueUpdateForm ),Navigate(CreateRecordForm))The strange thing that i have been struggling with is getting the order of the argument, i thought Navigate(CreateRecordForm should go before Navigate(IssueUpdateFormand using the ROW_ID="" i had been trying to use 0ThanksCarl