Bugfix: New Validation for Hyphen and Numeric Usage in Association Names

[hseligson]

Association definition names containing a hyphen (-) or starting with a numeric character cause issues for users querying associations via GraphQL. This problem affects all users who utilize associations with such naming conventions.

What’s Changing?

We are now restricting users from creating and updating association definitions with the following:

1. Hyphens (-) in association definition names.
2. Association definitions starting with a numeric character (0,1,2,3, etc.).

When a user attempts to implement hyphens or numeric values within the association name, the validation will return an error message with the following responses in the examples below.

For validation associated with a hyphen (-):

// Response error example
{
  "status": "error",
  "message": "Invalid association definition name 'invalid_definition_name'. Hyphen(\"-\") is not allowed in association definition name.",
  "correlationId": "84048eda-9743-4731-a0c9-bed28f1cc9a3",
  "category": "VALIDATION_ERROR"
}

For validation associated with a numeric character (0,1,2,3, etc.):

// Response error example
{
  "status": "error",
  "message": "Invalid association definition name 'invalid_definition_name'. Association definition name cannot start with a digit.",
  "correlationId": "84048eda-9743-4731-a0c9-bed28f1cc9a3",
  "category": "VALIDATION_ERROR"
}

This validation will not impact existing association definitions. When users create a new association definition or rename an existing one, the user will be required to comply with the new naming convention.

The expected date this validation will be enforced is November 9th, 2023.

Please let us know if you have any questions by replying below.