We have a custom entity that uses an alternate key that has colons in it, for example - "001:ABC:DEF". Queries to retrieve or update these entities are failing with "A potentially dangerous Request.Path value was detected from the client (:)".
What seemed to have worked last week, no longer works this week. Does anyone know if this change came in with the April 2019 update to D365 and is there any way to configure what is considered valid input?
Thanks!