First, I want to share that the search functionality within Magic ETL has been very useful.
I would like to propose an enhancement to further expand this capability.
Currently, when searching for a value such as a Product ID or specific field name, the results return locations where the string explicitly appears. However, in many cases, that field may be referenced, transformed, renamed, or incorporated into formulas throughout the dataflow. When working with large or complex ETLs, it would be helpful to identify not only where a string appears directly, but also where it is:
- Used within formulas (e.g., calculations, case statements, concatenations)
- Altered or transformed
- Renamed
- Used in filters or conditional logic
In short, an option to search for “usage and transformations” of a field—not just direct text matches—would greatly improve impact analysis and debugging within Magic ETL.
This enhancement would be especially beneficial when evaluating downstream effects of modifying key fields (such as Product ID, Customer ID, etc.) across complex dataflows.
Thank you for considering this request.
