Hello, i am not currently allowed to manage the data loading or modeling on the application but i have to create visualization boards for then. The question is, i have some tables or group of tables not directly connected but with common fields which i´d like to use to filter data and make some drills to make the visualizations i need.
Is there a way to perform this ? Which is the best (easiest) approach? I´d be gratefull for materials related to it.
to connect unrelated tables. But usually those datamodels are intentionally designed to apply such a logic. If it's not the case it's rather unlikely that you could do it within the UI. Beside the permission to adjust anything within the datamodel you need to understand how it's designed and why was it created in this way. With this knowledge you will know what you could do and what not - and if it's important in any way that the datamodel must be changed from someone.
It has nothing to do with the server or any configuration - the only counting point is to have/create a proper datamodel. Some weaknesses there might be bypassed within the UI but usually the needed efforts and knowledge for it are much higher as building a normal datamodel in which all data have a proper relationship (and if you could it make work it might be quite (too) slow).
Therefore my suggestion to solve the challenges on the cause and not on the effects.
From post what I can guess is you have tables but those tables are not linked but based on the tables(unlinked) you have need to create a chart, correct?
If yes, than you can create chart but that will of no use.. as data is not linked and when you filter or select the data chart will not response with proper data.
to connect unrelated tables. But usually those datamodels are intentionally designed to apply such a logic. If it's not the case it's rather unlikely that you could do it within the UI. Beside the permission to adjust anything within the datamodel you need to understand how it's designed and why was it created in this way. With this knowledge you will know what you could do and what not - and if it's important in any way that the datamodel must be changed from someone.
It has nothing to do with the server or any configuration - the only counting point is to have/create a proper datamodel. Some weaknesses there might be bypassed within the UI but usually the needed efforts and knowledge for it are much higher as building a normal datamodel in which all data have a proper relationship (and if you could it make work it might be quite (too) slow).
Therefore my suggestion to solve the challenges on the cause and not on the effects.
