Use case: When configuring fields in a data reader, it's not uncommon to forget a field (e.g., Customer Description in Screenshot 1 below), or the data structure may evolve, introducing new fields or changes in hierarchy over time. Currently, if a field needs to be added or repositioned, users must clear all existing fields and rebuild the entire list manually in the correct order. Or insert the missing field but it gets added to the bottom of the data reader.
You cannot simply insert or reposition a field (e.g., adding Customer Description into its intended place as shown in Screenshot 2). This can become time-consuming when creating/managing multiple or complex data readers.
Screenshot 1: Current state (missing field example)
Screenshot 2: Attempting to add a new field (unable to reposition)
Screenshot 3: Attempting to add a new field (field added to bottom of data reader)
Proposed Improvement: Introducing draggable field mappings in the data reader, allowing users to do the following:
- Reorder existing fields easily.
- Insert a new field between existing ones without having to clear the list.
This improvement could follow existing UI patterns, similar to dragging a new block into a layout with existing blocks, or using the reorder handle seen in entity custom sort configurations (Screenshot 4).
Screenshot 4: Example of draggable UI element in custom sort
Thanks for your consideration!
Hamza
