@Rutherford, Kristin As per my discussion with internal team, there is no workaround at this point. May be can’t we script-swipe all the special characters from the import template? The terms would still be recognizable.
But if you have any additional feedback to the product improvement, feel free to log it in IDEAS forum here - https://feedback.azure.com/d365community/forum/82d7bddb-fb24-ec11-b6e6-000d3a4f07b8 and do share the feedback link so that I can pass it to the respective product owners to further review it.
And also would appreciate if you could confirm from where did you get the terms from? and also please attach a sample template (remove any sensitive data) so that I can pass the same to the product team.
Hope this info helps.
Please don’t forget to
Accept Answer and
Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.
@Rutherford, Kristin Wanted to check if you have got a chance to see my previous response. If so, could you please help share sample template as requested.