La fonction de suggestion automatique permet d'affiner rapidement votre recherche en suggérant des correspondances possibles au fur et à mesure de la frappe.
I created a custom object in a new portal. The custom object only has one test instance at the moment. When I created the custom object, I specified several required properties. I have since decided only to have one required property (name). I ran an API patch call and successfully (I think) redefined the schema. However, I am unable to delete one of the formerly required properties (close_date). I have tried to do this from the CRM UI and from the API. The CRM UI tells me that I can't delete it because property is still a required property. Of course, the API delete endpoint doesn't give any meaningful response.
Any help would be appreciated.
Here's the output for the 'Get existing schema' endpoint for my custom object after patching it to change the requiredProperties value. You'll notice the only defined required property is 'name' :
So, I managed to figure this one out. I don't know if this is a new feature in Custom Objects since I first had the problem or if this was there all along and just not well documented.
The "required" setting preventing deletion was in Settings under the "Set fields seen when creating Projects" area under "Custom Objects." I clicked "Make it optional" there and voila! I can delete the property!
So the idea is to reset all the parts of the object schema where the old column is used (primary_display_property, required_properties, and searchable_properties in my case)
So, I managed to figure this one out. I don't know if this is a new feature in Custom Objects since I first had the problem or if this was there all along and just not well documented.
The "required" setting preventing deletion was in Settings under the "Set fields seen when creating Projects" area under "Custom Objects." I clicked "Make it optional" there and voila! I can delete the property!
@dennisedson I haven't yet figured this out. Here's my JSON patch request body. I'm pretty certain that it was successfully delivered/executed because originally, after I first created the custom object, when I ran the Get Existing Schema endpoint the requiredProperties property listed several properties. Unfortunately, I didn't save a copy of that output.