Flattening vs. using SQL tables in their native structure.
What is best to develop for Qlik sense when there are multiple SQL tables involved?
Basically ,to build an ETL process to extract the data needed, "flattening" the needed data into a single fact row and then connect to the dimensions needed, or to use the tables in their native structure, letting QLik navigate to all the relationships. (we have a replicated backup site so contention is not an issue ).
The one issue I found with flattening the data is bringing tables with different "grain" levels into a single row and the only solution I have is to "null" the duplicated measures at each level to one single row.