I've dreamed about this since Henry became a thing years ago. But how to do it? Think of this as a discussion board to gather requirements for this potential not-yet-planned project.
Here's one strategy...
1) If field unused in all explores, add hidden:yes and move it to a section of the file out of the way, or
2) If field is unused in one explore but not in any another, first hide the field in the view and move to special zone, like #1. Next create an extension of the view in which the field is unhidden and use that new extension view in the one explore which needs the field.
3) If a field is unused in one explore but used in all others, do the opposite of #2. Leave the field unhidden in the primary version of the view, but create an extension which modifies that field to hide it and use that extended view in the explore which doesn't want that field.
There are also other LookML tools, like using the fields: [] explore/join property or even perhaps access grants (then a quick attribute toggle could be used to hide/unhide), which could be used to address this question as well.
What features should this have? What design principles should guide its design?
I've dreamed about this since Henry became a thing years ago. But how to do it? Think of this as a discussion board to gather requirements for this potential not-yet-planned project.
Here's one strategy... 1) If field unused in all explores, add hidden:yes and move it to a section of the file out of the way, or 2) If field is unused in one explore but not in any another, first hide the field in the view and move to special zone, like #1. Next create an extension of the view in which the field is unhidden and use that new extension view in the one explore which needs the field. 3) If a field is unused in one explore but used in all others, do the opposite of #2. Leave the field unhidden in the primary version of the view, but create an extension which modifies that field to hide it and use that extended view in the explore which doesn't want that field.
There are also other LookML tools, like using the fields: [] explore/join property or even perhaps access grants (then a quick attribute toggle could be used to hide/unhide), which could be used to address this question as well.
What features should this have? What design principles should guide its design?