Been trying to wrap my head around the various columns collections situation and think I’ve come up with something of an idea… just putting this here for comment
Problem
its a long list, maybe we’ll add it here but we all know at least a few
Idea
columns have two properties field and title and we need a third for abstraction, say ‘role’ or ‘id’.
BEFORE (what we have today, grid column id assumed to equal field)
gridModel.columns = {
Part_PartNum: { field: "Part_PartNum", title: "Part #" },
Part_Description: { field: "Part_Description", title: "Description" },
PartLot_LotNum: { field: "PartLot_LotNum", title: "Lot" }
};
AFTER (defaults to field, but optionally abstracts the column away from both field and title)
gridModel.columns = {
PartNum: { field: "Part_PartNum", title: "Part #" }, //<-abstract
Description: { field: "Part_Description", title: "Description" }, //<-abstract
PartLot_LotNum: { field: "PartLot_LotNum", title: "Lot" } //<-default
};
This could make dynamic dataviews, grids, providers, views (especially based on BAQs) work better and provide potential for UI expressions that eval properly on dynamic dataviews. I’m sure there are implications across the framwork but perhaps better to climb out of the hole now than later.
Just a thought.