We're planning to do a bulk update to import external end user organization information.
We have a trigger in place that re-opens tickets when they are updated (for side conversations, specifically). I've noticed that when creating a new organization on a ticket, the ticket re-opens - I assume this is because ticket|organization is a ticket field, and not globally inherited from the end user. In other words, updating the end user updates from a ticket updates the ticket, but not other tickets; and that update is independent of actually submitting changes to the ticket. Am I correct there?
I basically get the logic there, but if I bulk update our user records, will this result in bulk re-opening of their tickets? Am I correct that pre-existing tickets still won't have an updated organization after the update, that it will only apply on a go-forward basis?
Please sign in to leave a comment.