Stop Conversion of '=' for next Page Trigger

Jan Malte Behrens

• May 17, 2023 11:50

In the export step at the beginning of the flow I'm building I need to specify that the Source uses Pagination by updating the Request Body. So I use 'Custom Request Body' in the Pagination Tab and fill it with the necessary information.

The Error now comes from the Response body having a '=' character for the next page which is autoconverted by Celigo to '=' which the Source can't parse and throws an Error.

How can I prevent Celigo from converting the special character or convert it back to a '=' before sending out the next page request?

0

• 

  Kathyana Rule Community moderator Technical Writer

  • May 17, 2023 14:18

  

  

  Hello Jan Malte Behrens, 

  I have moved your post to the Troubleshoot custom flows section for more visibility. Thanks! 

  0
• 

  Scott Henderson CTO

  • May 17, 2023 14:55

  

  

  

  Can you share screenshots of your export so we can see exactly where the characters are being converted? Can you also share a screenshot of your connection so we can see the media type being used?  Be sure to mask any sensitive fields that you don't want to show publicly.

  0

Please sign in to leave a comment.