Apex Code Development You need to sign in to do that
Don't have an account?
getworking Does SF ever re-use object key prefix of a previously deleted custom object
Hi all, I want to know if SF will ever reuse the same key prefix on a custom object that has previously been deleted or is it guaranteed to use a new one?
I know, that SF record IDs are globally unique and it will take many million years before SF runs out of them, but what about the object key prefix (or ID) within a single org?
For custom objects, the prefix is 3 characters long, case sensitive and alphanumeric which gives around 240k variations.
I know, that SF record IDs are globally unique and it will take many million years before SF runs out of them, but what about the object key prefix (or ID) within a single org?
For custom objects, the prefix is 3 characters long, case sensitive and alphanumeric which gives around 240k variations.
The custom object prefixes (or IDs) are in fact re-used.
The prefix seems to be sequential, so if you create a new custom object that gets prefix a01, the next one will get a02 and so on.
What happens with prefixes of deleted objects?
Well, while the object is not completely erased and is still in the recycle bin, the prefix will remain reserved. So if you delete a01 and create a new object, it will get prefix a03, however, if you erase a01 from the bin before creating a new object, the new object will get now released prefix a01.
Also, the name (and API name) of a custom object has no effect on the prefix that an object gets.
All Answers
The custom object prefixes (or IDs) are in fact re-used.
The prefix seems to be sequential, so if you create a new custom object that gets prefix a01, the next one will get a02 and so on.
What happens with prefixes of deleted objects?
Well, while the object is not completely erased and is still in the recycle bin, the prefix will remain reserved. So if you delete a01 and create a new object, it will get prefix a03, however, if you erase a01 from the bin before creating a new object, the new object will get now released prefix a01.
Also, the name (and API name) of a custom object has no effect on the prefix that an object gets.