Response mapping problem

Hi, I have a problem regarding response mapping.
I cannot proceed the data from the response mapping from http lookups, in the preview we can see that the data is mapped but indeed, when I check in the debug logs of the connection debugger we see that the fields are empty, so in fact, we don't actually process the data. I have added the pictures from the preview from the response mapping. I can see only the mapping that is proceed from the Webhook and not from the response mapping from the lookups. Please refer to the MasterOrderID element.

0

Comments

7 comments
Date Votes
  • Hi Zhivko Talevski,

    Please make sure that you don't have any PII (personal identifying information) or any secure information in those screenshots. So that we can help you faster on this, could you please open a support ticket? Thank you!

    0
  • Hi Zhivko Talevski,

    This will likely require more troubleshooting so definitely submit a support ticket. But our experts' first thought to help you troubleshoot was that you could map just data instead of data[0] as you did above. It looks like your lookups are returning empty data, so by mapping data, you will be able to explicitly see if the lookups are returning empty data. This is because the mapped array data -> GetOrderResponse will be visible as an empty array in the next flow step's retry data.

     

    0
  • Hi Courtney,

    Thanks for the reply.

    I have mapped as data[0] because from the API I always received one record so this is just to not have loop element in the next mapping screen. I didn't attached logs from the "GET Order" Lookup but response isn't empty and also when I do mappings in the "GET Master Order" Lookup I'm able to see response output from the GetOrder Lookup. From the preview mapping you can see that MasterOrderId element is filled with the response data from that Lookup, but as I mentioned above when I run the flow to test in the debug logs MasterOrderId element is send as empty string.

    I will submit a support ticket as you mentioned.

    Thank you!

    0
  • Zhivko Talevski were you able to figure this out? I have a different flow setup but the same problem - lookup data is sending as an empty string upon the final import

    0
  • Hi Ariel, 

    I have found solution in my case, don't know if you have the same issue but I am glad to help you if you wish.
    In my case I was working with API where the response was XML, not Json. I had an issue with the Resource path, I hade to use Local name function in order response from XML to work

    In my case

    Resource path -
    /*[local-name()='OrderDto'] (OrderDto is root element)

    Success path -
    /*[local-name()='OrderDto']/*[name()='diffgr:diffgram']/*[local-name()='OrderDto']/*[local-name()='Order']/*[local-name()='OrderId']

    Tell me more about your problem and I will be glad to help you

    0
  • Hi Zhivko Talevski,

    Looks like my challenge was a bit different than yours. When using 'one to many' in the lookup I had to enter a JSON path to the child. Then, it also asks for the expression for the 'ID' of the children. I accidentally included the JSON path to the child AND the ID in my 'id' field when it essentially puts those 2 fields together to get to the children IDs.

    All it was after was {{ID}} but instead I had entered something like {{results.associations.lineitems.ID}}

    0
  • Hi Ariel,

    Yes you have to be specific when using one to many path, however as I can assume you figured out how to solve your problem by yourself :)

    If you need anything you can freely ask me anytime

    Regards

     

    0

Please sign in to leave a comment.

 

Didn't find what you were looking for?

New post