The thing is, this should be a non issue. The client (browser) should not care about where a field comes from, only that it is marked updatable and what type it is. Any other logic is useless and buggy.
This should just work.
2 Likes
Agree. For clarity, by ‘inheritance’ I mean a half-dozen columns collections exist in the grid panel. Which override the others? There are ‘auto-load’ options that work or not, when? who knows? View models merge with provider model, either, both, neither have columns defined, what happens? who knows?
Case point:
Clear as mud right?
EDIT: just noticed something in the js - havn’t tried it yet. Does auto-load columns require Grid Model Columns be empty?
1 Like
…Not to mention user-personalization merges in as well.
imagine spending the resources it took to get clipboard-copypasta-update to ‘work’ instead of making solid and documenting grid/provider/view model & columns/personalize/filter/sort
now imagine the tech-debt to rework both to actually work.
/rant
Welcome to Kinetic!
3 Likes
That’s cute.
Are you new here?
4 Likes
FWIW, I bet its a field/alias mismatch or some broken parser trying to split baq fields on underscore.
a bunch of matching across column collections is on
column.field
You could put a breakpoint on buildColumn() and inspect whether/why erpEditor is undefined
I honestly don’t give a shi..
This is trash.
3 Likes
Can’t agrue w that logic. Just saying we’ll prolly have a libray of post-proc bpm ‘bug’ fixes for years before any of this is fixed. like:
2 Likes
There fixed it for you.
4 Likes