When creating an attribute definition we forgot to specify the data type as text and because the picklist values were numbers, the data type was set by the platform to decimal(2). This of course causes issues with my constraint model and rules. Interestingly enough I can manually set the attribute to string and fix the values directly in the CML, but this is no a great practice and someone has to remember do this like forever. I attempted to back everything out, deleted it and clear the recycle bin, but I assume there's a platform cache somewhere (like this velocity trailhead talks about
) that still has the original API name and when I try to recreate the attribute definition with the original API name, the platform appends a 1 to the end of the API name.
This is a brand new org and I'm using the feature code from the client's ERP so having a mismatch is a real pain in the neck to be doomed to from the beginning. Frankly, I would rather nuke the org and start fresh if this can't be resolved. I've asked all the smarties I know, but I know there are bigger smarties out there.
Plaze Halp! Danka
: As per the documentation, the system enforces API Name uniqueness even for deleted Attribute Definition records. You may raise a case with Salesforce Support to see if they can assist with resolving this issue.
