J Hook for filtering response - HTTP Get Lookup

David McDonald

• December 07, 2021 19:58

Hello, I've seen this post but it was not able to solve our issue: https://docs.celigo.com/hc/en-us/community/posts/360071486051-HOW-TO-Use-the-postSubmit-hook-to-ignore-specific-error-messages-?input_string=J%20Hook%20for%20Ignoring%20404%20Errors%20-%20HTTP%20Get%20Lookup

We have a number of different GET Lookups to get Products, Categories, and more from an API that we do not have control over. Whenever a GET call returns a result that is no longer in the system, it returns a 404. I tried both a postResponseMap and a pre-save J Hook function to set ignored = true, and I also just tried changing the response code to 200. Neither worked and we still have our Export showing tons of errors that aren't truly errors: 

 

Dynamics 365 Export to Our HTTPS Get Lookup:

 

We want to ignore the 10 errors in the Lookup:

Tried J Hook between the first two flows, and within the 2nd flow (with the errors) but it doesn't seem like I can intercept & filter that response? Please let us know if this is something that is possible without completely changing all of our flows.

 

Thank you

1

• 

  Kate Larson Senior UX Researcher Community moderator

  • December 09, 2021 18:04

  Hi David McDonald -

  Thanks for posting your question to the community. I'm checking with some internal experts on this, and hope to have more information soon.

  -Kate

  0
• 

  Kate Larson Senior UX Researcher Community moderator

  • December 10, 2021 16:45

  Hi David McDonald -

  Just a quick update to let you know your post has resulted in much discussion here at Celigo on how best to handle this scenario. We have decided that we should enhance our code so that in cases where a call to an endpoint results in an error (such as 404), the pre-save hook will be invoked. Note that this is currently the case for paginated exports, where we make multiple calls. If the first request is successful and second request fails with the 4xx, then we send these errors in the pre-save hook.

  I don't have a time estimate yet for when we will release this change, but I thank you for bringing it to our attention!

  -Kate

  1
• 

  Brian Kozub

  • July 22, 2022 22:50

  Kate Larson, has this been implemented, yet? Or is there an expected delivery date?

  0
• 

  Kate Larson Senior UX Researcher Community moderator

  • July 25, 2022 16:12

  Hi Brian Kozub (and David McDonald) -
  Yes, this was included in a maintenance release earlier this year. Sorry that we neglected to follow-up in this thread at that time.

  Thanks for checking, Brian!

  -Kate

  0

Please sign in to leave a comment.