Known Issues and Limitations

Names are case-sensitive when registering an asset, schema, or table.
If you change a previously registered asset (such as changing the data type of a field), when subsequently updating the asset on the platform, the change will not appear. However, if you update the asset a second time, the change will appear, allowing you to modify the asset on the platform.

Only an exchange administrator or the dataset owner (creator) may modify or delete a dataset.
If the dataset membership is restricted, only an exchange administrator, a member of the dataset, or the dataset owner (creator) may register, modify, or delete an asset within the specified dataset.
When registering an asset, the platform interprets Boolean data types as integer data types.

If there is an error when authenticating a connection, the error message may not contain enough information to indicate the exact cause of the problem. Please validate the connection URL, credentials, and TrustStore certificate are correct.

You must explicitly add all LDAP user groups and give them a role on the platform. This includes all nested groups.

Upon deployment of the platform, we recommend that you immediately configure the behavior of access control rules to allow or deny access. If however, you wish to change this behavior at a later stage, you must delete all access control rules prior to making this change.
The platform does not support Boolean data types and interprets them as integer data types upon asset registration. Therefore, you may only use the transformation types of Retain, Drop, and Redact with Null when accessing these data types. You may not use cell-level transformations nor access control policies with these data types.

Only an exchange administrator or the project owner (creator) may modify, delete, add assets to, or remove assets from a project.
When searching for users and user groups to add as members of a project or dataset, the search returns all enterprise users and user groups, including those who may not have access to the data exchange. The platform performs against the internal registry or the LDAP registry.
If a user who is not a member of a project attempts to query data in it, the platform may return a generic error that does not inform the user that they are not authorized to access the data.
When a project owner edits a published project, the project moves to In Draft status, preventing data consumers from being able to consume data until a data guardian re-approves the project.
When editing a rejected project, a data consumer can remove all but one asset. A rejected project requires at least one asset so a data consumer can re-submit it for approval.

When a data owner uses the REST API to create a new asset, the platform creates the asset in In Draft status, and a data guardian must approve it.
If you have an LDAP group with no users, the User Group API will return an error message.
Only an exchange administrator or the project owner (creator) may modify, delete, add assets to, or remove assets from a project.
Only an exchange administrator or the dataset owner (creator) may modify or delete a dataset.
Only an exchange administrator, a member of the dataset, or the dataset owner (creator) may register, modify, or delete an asset within the specified dataset.

If you already have LDAP configured to work with the platform, when upgrading from DSP v1.4.0 to DSP v1.5.1, set upgradeKeycloakFrom140 to true in the control-plane-values.yaml file as follows:
```
## Flag to patch ldap deployed 1.4.0 to 1.5.0
upgradeKeycloakFrom140: true
```

When changing the user role assignment of a user or group, it may take a few moments for the change to take effect. You should log in to the platform again for the changed role assignment to take effect.

In this section:

Release Notes