Support for special characters and language-specific characters in object-centric data model transformations (2024-06-14)

We’ve fixed an issue with our process for creating complete transformations from your scripts. Previously, if you used special characters and language-specific characters in your custom transformations and overwrites, the expanded transformation was marked with an incorrect character encoding which didn’t work. You can now go ahead and use special characters and language-specific characters in the SQL editor for transformation scripts, and we’ll support these in the transformations we create from them. Creating custom transformations has the instructions to write custom transformations.