liquid transformation

  • Liquid Mapping Issue when Input XML Contains Nested Nodes with the Same Name

    Liquid Mapping Issue when Input XML Contains Nested Nodes with the Same Name

    XML Input: <EVE>   <EVE>     <EVE.CAMS>       <EVE_CODE>20250806001</EVE_CODE>       <EVE_TITL>WPK -EVE TITLE EVI TEST</EVE_TITL>       <EVI>         <EVI.CAMS>           <EVI_SEQN>20250806101</EVI_SEQN>           <EVENT_TITLE>WPK -EVE TITLE EVI TEST</EVENT_TITLE>           <EVA>             <EVA.CAMS>               <EVA_CODE>WPK-01</EVA_CODE>               <EVA_EVEC>20250806201</EVA_EVEC>               <EVA_EVIS>20250806901</EVA_EVIS>               <EVA_SEQN>1</EVA_SEQN>             </EVA.CAMS>           </EVA>         </EVI.CAMS>       </EVI>     </EVE.CAMS>   </EVE> </EVE> Notice the nested EVE nodes, liquid is not able to navigate through this XML. For example this liquid assignment will not work: {%-…

    Know More

  • Testing DotLiquid Maps Locally

    Testing DotLiquid Maps Locally

    !UPDATE! Although the LiquidTransform project is useful it is not however running the Logic App dotliquid transformation code. The workaround still stands, where we have a map test workflow within each Logic App to test the transformations, until Microsoft releases the code, or someone reverse engineers the dlls used or Microsoft complete the mapping tooling…

    Know More