I need to trigger an external automation when a fact sheet is updated to set a parent.
I am observing that the FACT_SHEET_UPDATE webhook trigger consistently passes the parent as the event fact sheet in the payload, rather than the child that was updated.
Can I safely assume that the child fact sheet, whose parent was just set, will always appear as the last entry in the parent’s relation edge of type relToChild?
Best answer by Thomas Schreiner
Hi
Instead of the FactSheetUpdated event, I would use RelationCreated. if you want to be 100% consistent, also RelationSwitch (which is essentially a RelationDeleted and RelationCreated at the same time). From looking at FactSheetUpdated, there is no way knowing which child fs was added last.
Since this structure of events is somewhat confusing, in our Automation Platform we implemented the logic so that you don’t need to care about the event type, but you immediately get a list of created, deleted and updated relations plus the affected fact sheets, so that you can act on the actual thing you want to monitor (a parent being added) instead of thinking about how to get this information.
+3Hi
Instead of the FactSheetUpdated event, I would use RelationCreated. if you want to be 100% consistent, also RelationSwitch (which is essentially a RelationDeleted and RelationCreated at the same time). From looking at FactSheetUpdated, there is no way knowing which child fs was added last.
Since this structure of events is somewhat confusing, in our Automation Platform we implemented the logic so that you don’t need to care about the event type, but you immediately get a list of created, deleted and updated relations plus the affected fact sheets, so that you can act on the actual thing you want to monitor (a parent being added) instead of thinking about how to get this information.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.