You’re offline. This is a read only version of the page.
This is killing me, is it no way to roll up a related entity's field if they are a power fx formula column value?
WHY do they just keep dividing the feature??? this is killing everyone, this is so Microsoft, you introduce a new feature and it doesn't work with the old feature, and the old features are like ancient and as broken as they can be (re-calculate 1hr minimum, calculated field doesn't support simple logic statement)
I have spent so much time working on my app, I really hate this rollup field because it's so trash, so I have set up full set of Power Automate instant parent and child flow to calculate all my rollup field and have their master grand parent flow to trigger them under all sort of conditions, and it still has can't include the basic scenario that when a user deleted a row, Power Automate will not be no way to trigger the correct parent flow because Microsoft doesn't pass the previous value to Power Automate.
Now I am forced to go back to using roll up field and now I have to go back and change all my fiend to be the legacy calculated field? This is so much BS working with dataverse
just fixed it, using a work around:
make a new column, set a business rule to pass power fx value to that column at all time at any condition, PATCHED!
And yes, for each rollup of power fx column, you have to use an intermediate column, double the amount of work!
Cons 2: you have to use the intermediate column in your form, because business rule only runs on the form!
Another bangdage after another bangdage to do what Microsoft dumb team unable to do, this is causing a lot of production and maintainance cost, oh whatever I dont think they care
#1
stampcoin
17
#2
mmbr1606
15
Super User 2025 Season 1
#3
ankit_singhal
11
Super User 2025 Season 1
Share
Report
All responses (
Answers (
