When I import a CSV and map the fields, it imports correctly, but one of the fields has HTML tags in it to be used by a workflow. The HTML is stripped out after the import is finished. Is there a different way to format my CSV to preserve the HTML formatting as literal text? Should I URL encode the text and then run a liquid filter in the Expression Builder node?
Solved
HTML with Custom Objects
+1Best answer by AutomatedDuck
We solved the problem by URL encoding our message body and keeping it encoded until we run a web request where we use url_decode Liquid filter to pass it in the API call. We got confirmation that HTML gets stripped out if not encoded.
Can you give an example of one the of lines of HTML code that is getting striped out? This sounds interesting and wondering if it is something with their importing code or with how the API interacts with that those HTML code. It might need to have everything escaped.
+1We solved the problem by URL encoding our message body and keeping it encoded until we run a web request where we use url_decode Liquid filter to pass it in the API call. We got confirmation that HTML gets stripped out if not encoded.
1 person likes this
Reply
Join the Community
Already have an account? Login.
Sign in to the Community
No account yet? Create an account.
Social Login
Login with LinkedInor use your username
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.