When working with custom objects, I can define the schema for the object and let the customers fill in the information for those custom objects. If the requirements for the custom object change (for example new mandatory field), I can modify the schema to add a new required attribute. But when I edit one the existing records I get an error message because it has the definition of the old schema and doesn't accept the new required attribute. The solution by now is delete all the records created under the old schema and recreate them (and update any existing relationship records in some cases).
My suggestion is add in the API some mechanism that recognises the current schema of the custom object so all the records can be updated without deleted and creating them again.
Please sign in to leave a comment.