Avoid visualisation malfunction when columns are renamed

When you have a custom expression in a visualisation which contains ${} and you rename a column that is used in the expression, the custom expression is not valid anymore. I've contacted support and they say it's as designed, but I find this behaviour very annoying.

E.g. when you use the following expression: "First([Some Column]) as ${DocPropWithName}" to set the column display name from a document property, this fails when you rename [Some Column].

Interestingly, you can avoid the problem by using the "Name" column property of the column, but I think this is an ugly workaround:

First([${Data Table}.{Some Column}.{Name}]) as ${DocPropWithName}