How to DELETE a DataEntity entry in Dynamics 365 Finance and Operations having special characters

(0) Share

Report

Posted on by Neeraj D

I am facing an issue while using `oData` to perform CRUD operations with entities having special characters. For example, the oData URL to `GET` a SecurityRole is `/data/SecurityRoles('<security-role-identifier')`. If the `<security-role-identifier>` has special characters then the URL doesn't work.
I encode the `<security-role-identifier>` using the `java.net.URLEncoder` with 'UTF-8' encoding.

This handles few of the special characters but not all. As a workaround, I started using the the following URL, which worked for me:

/data/SecurityRoles?$filter=SecurityRoleIdentifier eq '<UTF-8-encoded-identifier>'

This resolved my issue for the `GET` operation. But, I am still stuck for the `DELETE` operation. The **DELETE operation doesn't support $filter query parameter** and hence the URL for DELETE is /data/SecurityRoles(<security-role-identifier>).

So my question is in general and not specific for D365FO -> how to support delete operation in oData having special characters.

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Neeraj D 85 on at

Like (0)

Report
Copy link

Link copied!

This Query works for GET - data/SecurityRoles?$filter=SecurityRoleIdentifier eq '%21%21%21%21%40%40%40%40%40%23%23%23%23%23%23%24%24%24%24%24%24%25%25%25%25%25%25%5E%5E%5E%5E%5E%5E%26%26%26%26%26%26%26*******%28%28%28%28%28%29%29%29%29%29----_____%3D%3D%3D%3D%3D%2B%2B%2B%2B%2B%2B%5B%5D%5B%5D'

But the Same query fails for DELETE -

/data/SecurityRoles(SecurityRoleIdentifier='%21%21%21%21%40%40%40%40%40%23%23%23%23%23%23%24%24%24%24%24%24%25%25%25%25%25%25%5E%5E%5E%5E%5E%5E%26%26%26%26%26%26%26*******%28%28%28%28%28%29%29%29%29%29----_____%3D%3D%3D%3D%3D%2B%2B%2B%2B%2B%2B%5B%5D%5B%5D')

I have also tried with:

/data/SecurityRoles('%21%21%21%21%40%40%40%40%40%23%23%23%23%23%23%24%24%24%24%24%24%25%25%25%25%25%25%5E%5E%5E%5E%5E%5E%26%26%26%26%26%26%26*******%28%28%28%28%28%29%29%29%29%29----_____%3D%3D%3D%3D%3D%2B%2B%2B%2B%2B%2B%5B%5D%5B%5D')

But still it fails. Any reasons for this and workaround to handle such scenarios?

Was this reply helpful? Yes No
Neeraj D 85 on at

Like (0)

Report
Copy link

Link copied!

It is my observation that, the Dynamics 365 FO services are not able to recognize following special characters during the delete operation:

Unsupported Characters: +, \, ?, /

If these are not supported during delete, then they shouldn't also be supported during CREATE.

For ex, + is encoded as %2B but still the I am getting 404 error when the unique identifier has '+' in it. So encoding is not helping.

Is there any way to fix this or this is the limitation from from the Dynamics365 FO?

Was this reply helpful? Yes No
Neeraj D 85 on at

Like (0)

Report
Copy link

Link copied!

An update on special characters that are not working during the DELETE operation that are directly passed in URL even after URL encoding: +,/,\,?,&,#

Was this reply helpful? Yes No
WillWU 22,363 on at

Like (0)

Report
Copy link

Link copied!

Hi Neeraj D,

Please try to replace these characters with the appropriate hexadecimal value.

The solution in CRM: community.dynamics.com/.../crm-odata-rest-queries-and-special-characters

Was this reply helpful? Yes No
Neeraj D 85 on at

Like (0)

Report
Copy link

Link copied!

No, its not working for a '?'. For example, this is the role entry I have which I want to delete:

{

"SecurityRoleIdentifier": "<SP`~Char>?:;",

"ContextString": "",

"AccessToSensitiveData": false,

"Description": "SP3",

"SecurityRoleName": "SP3",

"UserLicenseType": "None"

}

This the URL that I am forming (after URL encoding) : /data/SecurityRoles('%3CSP%60%7EChar%3E%3F%3A%3B')

to delete the entry. As you can see, all the characters are properly encoded. I have another role, just without a '?' and it works fine (both create and delete). Why is it not letting me DELETE this entry - I am getting "No route data was found for this request"

I agree that it is not the right thing to have such characters in the security role identifier, but my question is, if the FO is allowing to create it then why not DELETE it?

Was this reply helpful? Yes No