@Sameh Louka
Rough guess: 30 - 60 GB which includes dev, prod, and a data hub. However, the best way to size a model (or workspace) is do the math properly by determining the lists and modules you'll need. Count up the lists and their respective list items as well as the modules and the lists that will be needed for them, including the time dimension. Always include system modules for every list. And be careful with list items, each list item requires a minimum of 500 bytes + the format type. Here's an example of some lists and modules I recently scoped out just to give you some ideas..
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β¦
