@shlokhan
Well, at one end of the spectrum, best practices, suggests that you should only use the data hub for transaction data, pre-aggregations, and reusable transformations. This keeps the data hub snappy and, quite frankly, it works.
On the other end of the spectrum, is reality. Sometimes you just cannot avoid it but you should only use formulas, like variances, for example, as a complete last resort. One example might be a report that combines data from various workspaces and it's just more efficient to report it from the data hub because all the data is consolidated there.
There's a lot of conversation about this, no right/wrong answers, but your best strategy is to follow the PLANS methodology and be conscious of the pros/cons of your decisions.
Hope this helps.
Thanks a lot!
I have 2 lists used in modelling, In Input module I'm using subset of territories from Country List and subset of Regions from Flat list. But in Output module,Its reversed, I'm using subset of regions from Country list and subset of territories from flat list.How to derive the numbers from input to output module. I do have…
This shows all comments across all data to all users with access to the UX page. This is not appropriate for any UX which might contain security access sensitive data. Comments on grids and cards ARE security dependent. That works fine. But anyone with access to the page can open this Summary Panel and see ALL comments…
If anyone is aware of idea exchange ideas that are currently being evaluated by the product team, if you don't mind linking them here, would love to give them an upvote. Thanks!
