{"id":1060,"date":"2014-11-03T17:18:01","date_gmt":"2014-11-03T11:48:01","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=1060"},"modified":"2022-07-01T14:50:42","modified_gmt":"2022-07-01T09:20:42","slug":"how-to-handle-special-characters-in-fetch-xml","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2014\/11\/how-to-handle-special-characters-in-fetch-xml\/","title":{"rendered":"How to handle Special Characters in Fetch XML"},"content":{"rendered":"

Fetch XML, the easiest way to write complex queries to retrieve data by joining multiple entities.<\/p>\n

Though being the easiest, we were still stuck at a point where we didn’t know what to do. We were getting Invalid XML error.<\/p>\n

\"Invalid<\/p>\n

For quite some time we were wondering what could have caused this. Below is our Fetch XML.<\/p>\n

What is this XML for? Through this XML, we are trying to find the Forecast record with the specified Forecast Name.<\/p>\n

Code:<\/strong><\/p>\n

string forecastName = “City & Lights (Sample) December 2014”;<\/p>\n

string xml = @”<fetch version=’1.0′ output-format=’xml-platform’ mapping=’logical’ encoding=’Windows-1252′ distinct=’false’>” +<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 “<entity name=’new_forecast’>” +<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 “<attribute name=’new_forecastid’ \/>” +<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 “<attribute name=’new_name’ \/>” +<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 “<order attribute=’new_name’ descending=’false’ \/>” +<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 “<filter type=’and’>” +<\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0“<condition attribute=’new_name’ operator=’eq’ value='” forecastName + “‘ \/>” +<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 “<\/filter>” +<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 “<\/entity>” +<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 “<\/fetch>”;<\/p>\n

Things were pretty good till the time we didn’t have any special character in the forecast name (For this demo we have hard coded the Forecast Name, in reality it is dynamically created). Then came the sore part, we got a Forecast Name with a special character “&” in it. It took us around 45 minutes to figure out the reason of getting Invalid XML error.<\/p>\n

The reason for the Invalid XML error was the special character “&”. We need to encode the special characters before using it in a Fetch XML.<\/p>\n

Then, we tried encoding the forecastName. We used the below assembly & code to encode the forecastName.<\/p>\n

Assembly Used<\/strong>: System.Web<\/p>\n

Code Used: <\/strong>HttpUtility.HtmlEncode(forecastName)<\/p>\n

Now, we got the below error:<\/p>\n

\"Business<\/a><\/p>\n

While investigating this issue, we found that System.Web Assembly is not supported for Plug-In registered in Sandbox mode. And, HttpUtility.HtmlEncode(string) needs System.Web Assembly.<\/p>\n

Now, what? We are again stuck with special characters in Fetch XML, giving us Invalid XML.<\/p>\n

Hush! nothing to worry, we have WebUtility as our savior.<\/p>\n

What all things are we suppose to do now?<\/p>\n

Well, we just have to use a namespace and that`s it we are good to go.<\/p>\n

Namespace: <\/strong>System.Net<\/p>\n

Code Used: <\/strong>WebUtility.HtmlEncode(forecastName)<\/p>\n

\u00a0<\/strong><\/p>\n

Now, the final XML look like this,<\/p>\n

string xml = @”<fetch version=’1.0′ output-format=’xml-platform’ mapping=’logical’ encoding=’Windows-1252′ distinct=’false’>” +<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 “<entity name=’new_forecast’>” +<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 “<attribute name=’new_forecastid’ \/>” +<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 “<attribute name=’new_name’ \/>” +<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0“<order attribute=’new_name’ descending=’false’ \/>” +<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 “<filter type=’and’>” +<\/p>\n

“<condition attribute=’new_name’ operator=’eq’ value='” + WebUtility.HtmlEncode(forecastName) + “‘ \/>” +<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 “<\/filter>” +<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 “<\/entity>” +<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 “<\/fetch>”;<\/p>\n

The special characters in Fetch XML being the sore point once, now is very easy to tackle.<\/p>\n","protected":false},"excerpt":{"rendered":"

Fetch XML, the easiest way to write complex queries to retrieve data by joining multiple entities. Though being the easiest, we were still stuck at a point where we didn’t know what to do. We were getting Invalid XML error. For quite some time we were wondering what could have caused this. Below is our\u2026 Read More: How to handle Special Characters in Fetch XML »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,21,22,24],"tags":[269,795,823],"class_list":["post-1060","post","type-post","status-publish","format-standard","hentry","category-dynamics-crm","category-dynamics-crm-2013","category-dynamics-crm-2015","category-dynamics-crm-2016","tag-characters","tag-fetchxml","tag-forecastname"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t