locked
encoding and decoding attributes RRS feed

  • Question

  • I'm using the crmService Create in SOAP form.  I'm passing the contents of an ntext field which can contain characters like ampersand that XML can't handle.  I've tried encodeURI() and that works fine for getting it through the SOAP.  Unfortunately, those encoded strings are what I end up with in the new object.

    Is there a solution to this? 
    Tuesday, February 17, 2009 5:12 PM

Answers

  •  

    Take a look at the following post about using fetch with ajax. The sample has a method called FetchEncode which encodes an xml string that is passed as a parameter.

    • Marked as answer by mardukes Tuesday, February 17, 2009 8:18 PM
    Tuesday, February 17, 2009 7:18 PM

All replies

  •  

    Take a look at the following post about using fetch with ajax. The sample has a method called FetchEncode which encodes an xml string that is passed as a parameter.

    • Marked as answer by mardukes Tuesday, February 17, 2009 8:18 PM
    Tuesday, February 17, 2009 7:18 PM
  • Ah!  encodeURI provides the "wrong" encoding.  Why didn't Microsoft provide your function?!

    And a big 10-4 on the need for the OnGlobal area.  Even if it's in the ISV config, why isn't there a place to drop in Application and/or entity scoped functions?
    Tuesday, February 17, 2009 8:17 PM