Lol - those useless punks.
So Jose’s article is very relevant. It’s basically about making the underlying table that will be the holder of the EDV’s data. Add all the columns (and their types) for the data you need - since you are going to manually build this table, I would only grab the stuff I really needed. There is the possibility you could CLONE the data structure of the existing UDxxx (not the list) edv table. This would effectively give you EVERY column in a UD record (since the non-list version also shows UD).
Once the table is built, then you use the snippet from Jose to make an EDV for it - making it bindable to controls.
All done. Haha just kidding - that’s just the setup. Now you have to maintain the data in the table.
I envision placing an event on the LIST edv so that when it’s data changes, we update our table accordingly. Pseudo-code to follow:
One potential method - copy rows from the list
foreach (DataRow drtableOld in ListTable.Rows)
//now here you'd grab your UD fields manually - perhaps a DB lookup, or just looking in the adapter
Now that I’ve written that down - it seems like you might as well just look at all of the SysRowID of each record of the LIST, then just DB lookup those entire records while you’re at it and use that to populate your table. I am unsure of the efficiency.