Data Transformer step returning data as "forbidden"

[GSG]

Your Task History ID

https://connect.pabbly.com/task/history?filter_status=applied&filter_by_workflow_id=IjU3NjYwNTZmMDYzMjA0MzA1MjY0NTUzMTUxMzIi_pc

Hi

The workflow is https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTZmMDYzMjA0MzA1MjY0NTUzMTUxMzIi_pc

In step 6 (Data Transformer) the data for Res3 Message is being returned as 'forbidden'. We are not sure why. Can you offer some help to fix this so that the message entered by the customer is recorded here. It should read 'Happy Birthday'.

Thanks for your help

Graham

 

[Preeti Paryani]

Hello @GSG,

You can ignore the res3 response data and instead, map the data received under the res2 response keys.

Let me know if you need any further assistance.

 

[GSG]

Hi
We wanted to do that but the data for the 'message' is not being brought in, so we are unable to map it. See my attached screenshot. There should be a value for the message, but it is not there. Any ideas why it isnt there and available for mapping?

 

[GSG]

this is the data that is processed by the iterator in the step before. The display value for the message does not appear in Res2 iterated data, but the data leash set, eva case and ther other oiptions all comes through. for

{"id":100005,"key":"Gift Wrapping?","value":"Birthday ($10) $ 10.00","display_key":"Gift Wrapping?","display_value":"Birthday ($10) $ 10.00"},{"id":100006,"key":"","value":"Happy Birthday","display_key":"","display_value":"Happy Birthday"}]

 

[Preeti Paryani]

Hello @GSG,

Those values are being received under res1 data values. Please refer to the attached image for more information, and you can map the details from there.

 

[GSG]

Yes but when the order content is different Result 13 Value sometimes does not exist (as there are multiple options that a customer can select / ignore. If we map it to this value, most automations will fail as there isnt a Result13. This is why we have tried to map it against the specific value in Res 3

 

[Preeti Paryani]

Hello @GSG,

The response key for the specific value hasn't been sent by the trigger application (in your case, WooCommerce). We recommend contacting the WooCommerce team regarding this issue, as until the key for that specific value is received, it will not appear under the res2 response data.