Thank you! This was a great video. I started using an HTTP request but switched to this method instead. The only issue I ran into was PowerFx not finding my field (Dataverse source). If that happens to anyone else, switch to Open Component Library and edit the formula there and your field will appear!
Thank you so much Alex! I am not a Pro Developer and loved the clever use of fields and buttons to trigger flows. Only 'coding' aspect was to do some research on Fx Patch function :). Would be good to have more examples and videos for MDA's using Davaverse as all the training videos for Fx are based on Canvas Apps updating Sharepoint.
Love the use of the datetime field to trigger power automate, if you are happy triggering it more than once. I've typically used a yes/no column in the past to achieve the same thing but often have to reset it if I want them to be able to fire the flow more than once. I dont think you need to include the fields on the form as you are using the patch statement for the power FX button, which is updating the record via the API, not via the form. Could be wrong though
You made my day sir :) Appreciate your effort.
Thank you! This was a great video. I started using an HTTP request but switched to this method instead. The only issue I ran into was PowerFx not finding my field (Dataverse source). If that happens to anyone else, switch to Open Component Library and edit the formula there and your field will appear!
Thank you so much Alex! I am not a Pro Developer and loved the clever use of fields and buttons to trigger flows. Only 'coding' aspect was to do some research on Fx Patch function :).
Would be good to have more examples and videos for MDA's using Davaverse as all the training videos for Fx are based on Canvas Apps updating Sharepoint.
Love the use of the datetime field to trigger power automate, if you are happy triggering it more than once. I've typically used a yes/no column in the past to achieve the same thing but often have to reset it if I want them to be able to fire the flow more than once.
I dont think you need to include the fields on the form as you are using the patch statement for the power FX button, which is updating the record via the API, not via the form. Could be wrong though
Is there a way to do this without Dynamic 365?