Is there a way to union 2 tables when creating a chart. I currently have one table with a series of categories and another with a different series. I need to create a chart that will have a union of these tables. I know I could create a new table during the load but am trying to avoid this due to size of the current app and how much data I would be duplicating. Below is an example of the 2 different tables and what I am trying to archive. Please note that the structure has been simplified to demonstrate my example.
If you were to concatenate Table B onto Table A while adding a Category field with value W for the Table B data, where is the duplication? Also, even when there is duplication or denormalization, this isn't typically a problem for QlikView due to its compression.
Ecorrea, we'd only want your Table_Result table if we really ARE trying to get rid of the Product dimension completely. I'd guess we still want the dimension, just not in the chart. I agree with concatenating Table_B, however, which is what I was suggesting.
QueueWeRavn, I can't think of any good reason to leave these tables separated in the model. And if there IS a good reason (not evident from the fields we were given), I can't think of any good reason not to add the Category field to Table B during the load. Calculated dimensions tend to be slower than real dimensions, plus you then can't do things like select category W, though in some cases it IS an advantage to have a solution that doesn't require a reload, so good job there. Note also that we'll get a synthetic key either way. This isn't strictly a problem, but IS a hint that we should perhaps combine the tables.
