This relatively expensive method gets called in a number of different contexts:
- Update ChangeSetItem (may no longer be necessary with the new event driven approach)
- Update CMS actions
- Update tree flags
In most modification events, it gets called repeatedly against the same record. Seems like an obvious case for a cached result.
This relatively expensive method gets called in a number of different contexts:
In most modification events, it gets called repeatedly against the same record. Seems like an obvious case for a cached result.