Forum Discussion
If you enable the Null-safe evaluation, then you could follow this Mapper with a second Mapper to prune out the null or blank fields with a mapping like this:
Expression: $.filter((value, key) => value && value.trim())
Target path: $
See the Preview panels in this example:
So it seems to me that I need to use Routers and Joins to aggregate all of the mapped fields together from multiple REST Gets. Is this correct?
Hi mkramer,
Firstly, there must be a better way to query a customer’s data in the CRM system via the email address. Failing that, you might consider building a correlation db with the steps you describe. Then you can reference the database (maintenance will be an issue).
Secondly, if you do need to use the path described, note that there will be an “original” field on the output of each REST GET where you can access/remap the data that was present on the input.
Thirdly, as self-described “newbie”, make sure you fully understand the streaming nature of the document processing in a pipeline. I find that the realities of the streaming implementation are difficult even for seasoned/intelligent software developers to grasp initially. Getting a firm grasp on it will help you see what you need to do with that data.
-TK
Hi TK,
Thanks for the tip. This made me look deeper into the REST API of the system I’m trying connect. There is a query option and I have the syntax working in Postman but when I copy and paste the syntax into a REST GET, it errors and says it’s a bad URI. Any advice on why a query like this would error? It’s clearly something syntactically wrong but I’m not sure what it is:
“https://.com/services/rest/connect/v1.3/queryResults/?query=select * from contacts”
Failure: The provided URI is invalid: https://.com/services/rest/connect/v1.3/queryResults/?query=select * from contacts, Reason: The provided URI is invalid: https://airborn--tst1.custhelp.com/services/rest/connect/v1.3/queryResults/?query=select * from contacts, Resolution: Please verify the provided URI and parameters are syntactically correct
Related Content
- 4 years ago
- 4 months ago