Inserting a table column screws up other column bindings

[Ryan_Deardorff]

I just tried using the "Add after" option to insert a new column into a table, but it screwed up all the bindings of columns to the right because apparently those bindings are stored based on column index, which doesn't get updated. The only way I can think of to fix that is by manually copy/pasting all the bindings from one to the next, which is a pain.

Version 8.1.36

[pturmel]

What kind of binding is this? Or do you mean in the props.columns of a table? If so, yes, you will have to manually move them.

[Ryan_Deardorff]

Sorry, yeah, it's props.columns

[pturmel]

If all of the bindings are pulling from your query dataset, consider dynamically generating the entire props.columns list using the dataset's metadata. Some techniques:

Automation Professionals' Integration Toolkit Module

I have spent my holiday poking at this. Wanted to provide an efficient replacement for a common use of python transforms: Make a (Perspective) table that dynamically populates both .data and .columns from source dataset that isn't constrained to any particular structure or data types. In Vision, one can achieve this (mostly) by pre-populating the column attributes dataset with all of the possible column names your application might deliver. No such thing in Perspective. But a transform can …

(Whether you use my toolkit or not.)

[cmallonee]

You could also just update to 8.1.39, where we fixed this undesirable behavior.

[pturmel]

@cmallonee

we fixed this

Huh. How did I miss that?

[cmallonee]

I'm not sure. Seems like you should spend some more time keeping up to date with all the minutiae of our development and release.