I have an automated system that, when triggered, uses information associated with the trigger to run a query and update another record based on the result of that query.
There are a few fields related to the query that contain ampersands (e.g. "System 1&2") that must be matched for the automation to work. If I attempt to send a message with the ampersand unescaped (e.g.{22.EX.'System 1&2}), it fails because it is invalid XML. If I try to replace the literal ampersand with escaped versions that should be valid XML (e.g. {22.EX.'System 1&2'}, {22.EX.'System 1&2'}) QuickBase returns no error, but the query doesn't find what I expect it to, ostensibly because the escape character isn't then decoded back into an ampersand on the other end.
I searched and searched and couldn't find any guidance on this issue for QuickBase in particular because for other systems, these escape characters seem to work.
Thanks in advance for your help! Hopefully someone knows how to get around this, aside from replacing all the ampersands in our tables with some XML-conforming substitute.
Question
How do I encode ampersands located in an XML Do_Query field string so that they get properly decoded on Quickbase's end?
This topic has been closed for replies.
Sign up
Already have an account? Login
Login to the community
Login with Quickbase US – quickbase.com Login with Quickbase EU – quickbase.eu
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.