Hi everyone,
I'm getting started with Azure Logic Apps as my team prepares to transition our integration layer over to it. During discussions, it seems there's a preference from management for using Liquid for data transformation tasks. However, I'm having a hard time with Liquid's syntax—it appears quite limited, especially since implementing NOT statements requires some unconventional workarounds, and it doesn't offer straightforward chaining capabilities like "if A and (not B)". This is quite different from our previous experience with Mulesoft's Dataweave, which felt much more flexible.
Am I overlooking something big here due to my inexperience, or is inline JavaScript genuinely more suitable for complex data transformations than Liquid? What are the real advantages of using Liquid? Additionally, can reusable JavaScript scripts be used multiple times, or are we restricted to only using .liquid files?
1 Answer
If your main goal is to keep things low-code and visual, you might want to stick to Logic Apps' native features. It's designed for this kind of work, and using visual tools can make management happy. Have you checked out the data mapper? It's somewhat similar to the drag-and-drop functionality in Mulesoft, but it might not handle the complexity of your transforms well. Just a thought!
Yeah, management sees Logic Apps as similar to Mulesoft, which is good to hear. I did look at the data mapper, but I don't think it has enough capabilities for our complex needs. I'll definitely keep exploring!