Magic / ETL Feature

The feature to allow schema changes needs to be applied to Magic as is in the workbench, but enhanced to do the following:


It should be tied to the coulmn ID of the source file so that if the name of the column in the dataset changes, it doesn't break all of the cards attached to it just because you rename simply says oh, hey, I see you have a new name, but yur ID is still XXXX, let me change that without complication for you!!!!


Currently the card will break and you have to go in and drag the new column over to fix it. A beast mode can re name, but it makes for a better use case if applied at the dataset level through magic....



1 votes

· Last Updated


  • There is an issue when many tables or transforms are joined with the same names, where the system renames the incumbant dataset's fields, instead of the new ones.  It gets very messy and error-prone. 

    Breaking Down Silos - Building Bridges
    Check out my video!
    **Say "Thanks" by clicking the heart in the post that helped you.
    **Please mark the post that solves your problem by clicking on "Accept as Solution"
This discussion has been closed.