Skip to main content

When using ExcelStyler early on in your flow (I use it to highlight invalid values in Excel fles right after the data has been read from my database) or any transformer that creates <attributename>.something “sub-attributes” (not sure what the actual name would be), you currently must make sure to manually rename all of those alongside the main attribute whenever you rename them through an AttributeManager or AttributeRenamed, otherwise they will not be observed by downstream writers and transformers. If the Styler is added in the later stages of building the flow, that means going through all downstream AttributeManagers one by one to make sure the newly added sub-attributes follow the main one.

It would be conveinient if those could all be renamed together automatically whenever the main attribute is renamed.

Be the first to reply!