Custom objects: Announcing schema functionality changes starting November 12, 2020 at 10AM PT

Background

Sunshine custom objects currently have loose schema enforcement rules. For example, object records are not validated against their object type. On November, 2020, at 10 am PT, we'll change this so that records created with custom objects are properly enforced by their schemas. Custom objects use JSON Schema, an extremely flexible format, and we will be refining the functionality we offer with that format. 

What's changing?

• The additionalProperties: false property will be applied to all schemas. This will prohibit adding non-schema properties and data to records. If you have non-schema data in your records today, you'll still be able to access it for reading. However, if you want to update any records with non-schema data, you'll need to remove the non-schema data with the update.
• The underscore character ( _ ) will be rejected when used at the beginning of a type or property name.
• The asterisk character ( * ) will be rejected when used by itself as a type or property name.
• Empty schemas (one with no properties) will be rejected. 
• Empty strings for property names will be rejected. 

Customer communications

We have run checks on our database to identify any customers who could potentially be impacted by these changes. We will be reaching out early next week to connect with anyone who will need more time to align.