Greetings & Welcome to Microsoft Q&A forum! Thanks for posting your query!
Apologies for the delay in response.
Thank you for the additional context. It seems the issue lies in how Dynamics 365 CE interprets and validates certain characters during the data import process, even though these characters worked without issues in your previous setup with SQL Azure. To address your specific points:
Encoding Configuration Dynamics 365 CE expects UTF-8 encoding by default. However, the Copy Data activity may not explicitly handle characters like ğ
properly if there are invisible control characters (like 0x1F
) embedded in the data.
Here's how you can ensure correct encoding throughout the pipeline:
Source Dataset (SQL Azure) - Ensure the source dataset uses UTF-8 encoding. This is typically the default, but you can double-check in the dataset's advanced settings.
Sink Dataset (Dynamics 365 CE) - Since Dynamics 365 CE expects UTF-8, no additional encoding settings are needed in the sink. However, invalid characters must be handled before reaching this step.
For more details, please refer: Manage invalid characters
Please refer to the thread link for similar issue, which might help you in getting some valuable insights.
Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
I hope this information helps. Please do let us know if you have any further queries.
Thank you.