@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!
There was an error rendering this rich post.
Hi all, The Client ID and Client Secret are available, intended for uploading and downloading files. Could anyone advise how to use these credentials DIRECTLY to make API requests? Thank you!
I have A6 as the parent list and two sibling lists: A6.5 and A7. The A7 list includes an attribute that maps to A6.5. In the UX, the user will select A6.5 using a content selector, and the grid (dimensioned by A7) should display only the A7 items associated with that selected A6.5. Since the selector is a page context andβ¦
