ToRecord() limits?: For a number of reasons (awkward webservices th

ryanh over 9 years ago

ToRecord() limits?:

For a number of reasons (awkward webservices that can't be changed by us, perceived performance issues with XPathSnippet on large record sets, etc.) I am parsing some webservice calls using the ToRecord() function in 7.6.

Question 1) If the external webservices we call start adding new/extra keys to the xml that weren't there when our CDT was designed will the ToRecord() still work when converting the new XML structure (with extra keys) to our CDT?

Question 2) One of the reasons to use ToRecord instead of XPathSnippet was because we may receive as many as 200 deeply nested/complex structures in 1 webservice call and need to parse this. We were worried that a) coding difficulty b) performance might be an issue when using the XPathSnippet versus ToRecord. Is this a fair assumption? We can't use the existing Appian built smart services partly because of 'includes' in the wsdl....

Discussion posts and replies are publicly visible

Parents

0 Mike Cichy
Appian Employee
over 9 years ago

Ryan, I apologize but I misread your question. I did forget that you are getting the output as text.
I would expect toRecord to work the same way as passing CDTs by value: it will support additional attributes and loosening of restrictions but not removals, or changes in data types, etc.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Mike Cichy
Appian Employee
over 9 years ago

Ryan, I apologize but I misread your question. I did forget that you are getting the output as text.
I would expect toRecord to work the same way as passing CDTs by value: it will support additional attributes and loosening of restrictions but not removals, or changes in data types, etc.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data