Is there a way to delay Triggers on tables executing until the dataspace they are in has been merged back to the parent

[Mike Nicol]

I have two dataspace, Item and Menu.

In Item, I have tables:

- Item (Item we sell)

- OptionSet (Option sets available)

- ItemOptionSet (Which option sets apply to which items)

I have a trigger on ItemOptionSet that creates records in the Menu Dataspace (MenuItemOptionSet) when a record is created. It creates records, or deletes them, to automatically assign OptionSets to Item on all available menus, which the data steward can then tailor by deleting unwanted OptionSets at Menu level. I have another trigger on MenuItemOptionSet which creates records in MenuItemOptionSetItem (which items within the optionset apply to this item on this menu).

The problem I am having.

In a workflow, the ItemOptionSet record added is in a child dataspace and therefore does not exist in Item dataspace yet. The trigger fires correctly and creates records on MenuItemOptionSet. However, when the trigger on MenuItemOptionSet executes, the association looking at Item dataspace for members of that OptionSet finds no records, as the child dataspace has not yet been merged.