You’re offline. This is a read only version of the page.
185
I have a roll-up and a calculated field on the Person entity that are working beautifully. There is now a request, however, to trigger a workflow from the calculated field. This is not allowed. Has anyone come up with a workaround for this?
More details:
The rollup field is Total Transfer Hours, which contains the total number of hours/credits transferred in from all prior colleges.
The calculated field is Eligible for Online Orientation. It is calculated based on the Total Transfer Hours (if > 24 it is Yes, else No).
I've created an Eligible for OO Copy field. I thought I could:
- Create a workflow that ran once an hour (after the Calculate Rollup Field process) that would copy the calculated Eligible for Online Orientation to the Copy field.
- And, to handle the situation where staff recalculate Eligible for Online Orientation immediately, I thought I could create a workflow that is triggered by a change to prior college Transfer Hours field. It would wait a minute then perform the copy.
I think there is probably a better way to handle this, though.
Do you have any suggestions?
Thank you
Hello Ijc,
Thank you for raising this topic again.
A while ago I had received a ticket regarding this pointing to another post in Community on the same subject
According to the documentation, a rollup has a limitation of not being able to trigger an workflow, the reason behind is because it doesn't have the same event pipeline as a normal field during the update process.
I managed to work around it with a recurrent flow, which will retrieve the records of the associated entity and filter them based on a copy of the field, comparing with the field value of the rollup field with the copy of it and after that it will set the value for the copy of the field based on the value of the rollup.
Unfortunately this method has a limitation because a flow by default is not able to retrieve more than a certain number of records, the way you can work around it is to create filter for the list records.
Looking at the calculated field documentation available below, I can see it also can not trigger an workflow:
"You can’t trigger workflows or plug-ins on calculated fields."
https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/define-calculated-fields
The post I mentioned above is available here:
At the time I've tried to find other workarounds as well for the documents above but for my test instance I was not able to trigger an recurrent workflow because the option was not available for me, probably it has something to do with the instance itself.
Additionally you can try an workflow with a plugin and a bulk delete, but this entire implementation will be more time consuming than the workaround you found which can be implemented using flow as I explained above or using an workflow.
I hope this helps.
Share
Report
All responses (
Answers (
