Great solution!!! Quick follow-up question: How can I trigger the rollup recalculation on the deletion of an associated record included in the rollup. When the "When a row is added, modified or delete" trigger action activates on a record delete, the associated GUID is not passed through the trigger causing the flow to fail.
Great Question! This is a bit more involved, but basically you'd need an dataverse "Action" which calls a classic workflow to grab the pre-deleted values from the record. Then your Cloud flow's trigger would be "When an Action is performed" as opposed to "When a row is Added, Modified, or Deleted". There's a great step by step blog on how to accomplish this here: forwardforever.com/power-platform-and-classic-workflows/
Absolutely, that would be advised. You would create Environment Variables for your App ID, Base URL for the HTTP action, etc... anything that would be different from one Environment to another
Great video, thanks!
Great solution!!! Quick follow-up question: How can I trigger the rollup recalculation on the deletion of an associated record included in the rollup. When the "When a row is added, modified or delete" trigger action activates on a record delete, the associated GUID is not passed through the trigger causing the flow to fail.
Great Question! This is a bit more involved, but basically you'd need an dataverse "Action" which calls a classic workflow to grab the pre-deleted values from the record. Then your Cloud flow's trigger would be "When an Action is performed" as opposed to "When a row is Added, Modified, or Deleted". There's a great step by step blog on how to accomplish this here:
forwardforever.com/power-platform-and-classic-workflows/
Just what I needed, do I need an environment variable when using pipeline deployment from sandbox to production. Thanks
Absolutely, that would be advised. You would create Environment Variables for your App ID, Base URL for the HTTP action, etc... anything that would be different from one Environment to another