Great idea to add this option - It would be a very useful feature

I'm also waiting for this feature

I saw this warning window, but a few months ago I was creating a test subject area using a union, and checking the option 'This source should be combined with another source at this level' was enough. I didn't fill out the 'fragmentation content' field then, and while the warning window did pop up, the area worked…

I didn't think fragmentation content was an absolute requirement. I did the trick of adding a new logical column as you described above, and the subject area works as expected—the returned records come from both tables, and even the logical dimension is joined correctly. The logs in the administration panel look…

I'm using OAC, and the problematic logical table is a fact table. Yes, retrieving tables from two different databases is definitely not the most efficient, but fortunately, these tables aren't large (640 and 1200 records).

Hi @Gianni Ceresa Thank you for your reply. I'm aware that UNION isn't the most natural approach here, but we have two tables from two different databases (so they're from two different connection pools). We don't want to do ETL to export the table from one database to another, so the most convenient solution seems to be…

Hi I encountered the same problem as Erik. The table structure is also the same, the priority group is 0, and the mapping is correct. I'm using the first option suggested by Federico, and despite checking the "This source should be combined with other sources at this level" option when creating an analysis, I always…