Today I was migrating my older OEID 3.0 applications to 3.1, and I noticed some of my older version views are not working anymore in new version.
We used to have multiple Bulk Add/Replace (without specifying Collection Keys) and we could use any attributes from any of these, in a certain View for example.
My views were like SELECT SUM("an attribute/metric from Bulk Add_1") / SUM("an attribute/metric from Bulk Add_2")
Now that you have to specify a FROM clause in your views, and it has to be from a certain Data Set, whats the best way to achieve above line goal?
It's hard to say what may or may not work for you given the amount of information you've provided. Multiple select views should work (with some limitations) but it's hard to say if those limitations would matter to your users. I don't know what you mean by cross joins being created.
We've solved this a few different ways going back to version 1.6 of the product but the techniques, ingest architecture, user experience, etc. vary based on requirements. In the example you provided, the multiple view approach should work. If it's not working (or not performing), we'd need a lot more context to help.
What I meant by Cross Join is Cartesian Product in situation that you have many-to-many relations between 2 Data Sets
Lets say, I have to different data, coming from 2 totally different source, one from Sales Dept and the other one from Purchase Dept:
|Part Number||Sales QTY||Sales Date||Part Type||Manufacturer||Country|
|Part Number||Purchase QTY||Purchase Date||Part Type||Manufacturer||Country|
What is the preferred approach to ingest this data?