Yep it can! Here is the powerfx code I used: ForAll(Self.Selected.AllItems,Patch(Orders,ThisRecord, {HoldButton: "Remove Hold" & Rand()});Notify("Hold in progress",NotificationType.Success,4000)) Just make sure you make the buttons visible if multiple items are selected!
@@D365Goddessthank you for the fast reply. This works, only Problem is it tells me my created column does not exist. I can still access the column in the table structure and I published the table.
This is a custom control that is called “associated grid control”. I mentioned it in this article: d365goddess.com/spice-up-your-case-forms-with-new-controls2/
The main purpose of the video was to demonstrate how you can use a custom button to trigger a power automate flow. This example happens to be changing the status of a record because someone requested that, but it could be anything a flow can do. Usually keeping it simple gets the point across.
Always great videos ! How can we modify the caption of the butons like (Create) into french. not the custom ones, I mean the managed bnts ? thanks in advance
@@nizarhaddaji918 Not sure if this is possible, have you installed the French language pack? I would think it will update the buttons to French but I haven’t tried this myself
The flow will run when the data in the hidden column is saved to dataverse, and that’s after the button is clicked. If there would be an auto-save the flow wouldn’t run again because the value in the hidden column hasn’t changed, unless the button is clicked again.
This is exactly what I was looking for a while ago. I just sucked it up and learned how to put a button on a canvas page lol
Oh no sorry the video came out too late!
@@D365Goddess it’s still a VERY helpful video and answered a question I’ve had for months. Thank you so much for covering this. Glad I subscribed!
@@RamzyTheDad Glad to hear it! Me too!!
Can this work when selecting multiple rows? Im trying to wrap a ForAll around AllItems but cant get it to Work.
Yep it can! Here is the powerfx code I used:
ForAll(Self.Selected.AllItems,Patch(Orders,ThisRecord, {HoldButton: "Remove Hold" & Rand()});Notify("Hold in progress",NotificationType.Success,4000))
Just make sure you make the buttons visible if multiple items are selected!
@@D365Goddessthank you for the fast reply. This works, only Problem is it tells me my created column does not exist. I can still access the column in the table structure and I published the table.
For anyone wondering: I had to go into the component library and construct the button there. Now it works 👍
@@herroxxxxxNavigate to 12:45 in the video and follow those steps then try again.
@@D365Goddess damn im so impatient hahahaha :D feel like a fool for not watching the entire video before. Thanks a lot :)
Great video as always! 👍 If I may ask, what is the component/control you are using for Opportunities/Quotes/Order tabs in the beginning?
This is a custom control that is called “associated grid control”. I mentioned it in this article: d365goddess.com/spice-up-your-case-forms-with-new-controls2/
Awesome! Thank you very much! 👍😊
You’re welcome @@marcuspaivio
Why not directly update status reason? Why do you need the flow if its just updating a different field on the same table?
The main purpose of the video was to demonstrate how you can use a custom button to trigger a power automate flow. This example happens to be changing the status of a record because someone requested that, but it could be anything a flow can do. Usually keeping it simple gets the point across.
Always great videos ! How can we modify the caption of the butons like (Create) into french. not the custom ones, I mean the managed bnts ? thanks in advance
@@nizarhaddaji918 Not sure if this is possible, have you installed the French language pack? I would think it will update the buttons to French but I haven’t tried this myself
But if the form automatically saved they flow will run again
The flow will run when the data in the hidden column is saved to dataverse, and that’s after the button is clicked. If there would be an auto-save the flow wouldn’t run again because the value in the hidden column hasn’t changed, unless the button is clicked again.