migration of Tickets Issues Incidents from acme to spd instance preserving original work ID numbers and timestamps
ART-997_KNOWLEDGE_NODE-26
is built upon the core tenancy keys (e.g. dev_org), we have a ton of flexibility, clarity and overlap avoidance.\n\nFor example, look at the following 2 IDs from the above examples:\n\n\n  don:core:dvrv-us-1:**devo/55**:issues/789\n  don:core:dvrv-us-1:**devo/44**:issues/789\n\n\nThese are issues from 2 different orgs, they have the same issue ID, but because of the devo in the DON they are both globally unique. This allows us to keep the type ids clean but still maintain a globally unique ID
How to Write an Object Model That Doesn't Suck