Data mapper improvements

This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .

This past November, we announced the general availability of our Data Mapper, a tool for developers to perform data transformation tasks inside of Azure Logic Apps. Through customer engagements, we have gathered valuable feedback and are ready to share some enhancement plans to address this feedback. These updates streamline data mapping tasks, rendering your workflow more intuitive and efficient. Let’s explore the new features and discuss how these changes can improve your data mapping experience.


Please let us know what you think in the feedback section. Your feedback helps shape future updates.



  1. Create data map

    Upload a new schema or select an existing one. The source schema, previously floating, now docks on the opposite side of the destination schema, enhancing visibility.

  2. Map a property to another property

    Use drag-and-drop to assign source properties to destinations.

  3. Understand a property type

    Hover over a property to discover its data type.

  4. Add a function then map to properties
  5. Function chaining

    Address more complex requirements by chaining functions together. Collapse the functions together to save valuable real estate.

  6. Rename functions and add notes
    To reduce complexity, we now allow function renaming for clarity and the option to add notes. This prevents confusion and makes editing and reviewing more straightforward.

  7. Reorder source properties
    Add static values and reorder properties to refine output at destination

  8. Expand/collapse hierarchy
    Support for complex schemas includes starting with nested properties in a collapsed state and expand as required to access deeper properties.

  9. Adjust width of side panel
    Modify a side panel’s width to address scaling for deep schema trees.

  10. Search within a schema
    Search functionality to discover specific elements  
  11. Favorite function
    Pin frequently used functions for quick access.
  12. View underlying code 
    Open the YAML file in read-only mode to read the code that powers the mapping process.
  13. Test map
    Select an existing source payload matching your schema type and check whether the mapper yields desired output.
  14. Understand if there has been an error
    Easily detect and address errors during mapping

Conditional mapping and looping improvements to follow in next part soon. 


Please use this questionnaire to provide detailed feedback or file a feature request using the Data mapper tag on our GitHub Issues.

Leave a Reply

Your email address will not be published. Required fields are marked *


This site uses Akismet to reduce spam. Learn how your comment data is processed.