here’s some examples. 1. and 2. works, but 3. I don’t think is possible to work with.
- Get the type, or category of the item and depending on that, choose a data table to work with. Works great.
- If you wish to store the data table as a reference, you can query if that reference == the data table you have in mind. If it does, use a (not THAT reference) data table. It works, but really just use method 1.
- The problem is that if you have two data tables based on different data types, and you input a data table reference into the “get data table row”, what data will you get to work with? I don’t know how this works in c++, but in blueprints we have pins of various types that needs to be correct.
So sure you can store a data table reference inside a master table, to determine which data table to use. But really, that’s just a convoluted method of 1.
Saying that a data table reference is useless was incorrect, (since you CAN query, or you CAN have 2 different DTs with the same data) but they can not be used for as much as we might want.