Forum Discussion

christwr's avatar
christwr
Contributor III
7 years ago

Issues with Base64 Decode - Base64.decodeAsBinary()

Curious if anyone has any thoughts or can see if I’m just doing something wrong… I have a pipeline that’s fetching content files from Salesforce. These are received in BASE64 format and need to be...
koryknick's avatar
koryknick
Employee
2 years ago
Copy LinkReport

alex_panganiban - you can also use the "When errors occur" property in the Views tab of the CSV Parser snap to ignore errors during parsing or even route bad records to an error view and handle them more gracefully.

Hope this helps!

 

  • Abhishek_Soni37's avatar
    Abhishek_Soni37
    Contributor
    3 years ago
    Copy Link

    Hey @acatlan ,

    In the Has next input box, you are passing the value as a string, remove the quotes.

    Let us know if it works!

    • acatlan's avatar
      acatlan
      New Contributor II
      3 years ago
      Copy Link

      Hi @Soni37 ,

      When I remove the quotes I get the following:

      I can run it with the error but it doesn’t return the next batch.
      I’ve also ran it without the quotes and without the “=” sign selected it doesn’t return an error but it doesn’t go to the next batch.

      • Abhishek_Soni37's avatar
        Abhishek_Soni37
        Contributor
        3 years ago
        Copy Link

        Hey @acatlan ,

        As per the workable document link you shared paging.next will contain the URL of the next result set.

        You need to make below changes:

        1. Has next should be an expression or a key that returns true or false. Below expression will check if the path exists in the response.

        $.hasPath(“$entity.paging.next”)

        In the Next URL, you need to use the URL that was provided in the $entiity.paging.next.

        You may need to adjust the URL or the expression as per your need.

        I hope this helps.