CRM Imports API - New validation for Required Properties

CRM objects often have properties that are required for creating records of that object type. For example Deals, require a Deal Name. When using the CRM Imports API, we're going to start validating that the provided import Request contains the properties necessary to create new records for the selected object types. This validation will only occur when the importOptions map has a value of CREATE in the importRequest.

What's changing?

Once this validation rolls out, any Imports API requests that include importOptions set to CREATE, and the required properties for that object type are missing, we will return a 400 error. The error message will indicate which properties and on what object are missing.

• If the import as a whole is missing a required property, we'll reject the API request from the start.
• If the import provided the required property as a column, but one of their rows has a blank value for that column, we'll fail just that row.

You should build your application to ensure required properties on objects are set.

When is it happening?

This change goes into effect on January 20th, 2025. We consider this to be more of a bug fix than a breaking change and will prevent unexpected results from apps using these APIs.