Currently, using SELECT statements in formulas for native versions - Actual/Forecast. But, this will not work with ALM, so what should be an alternate approach for looking up native versions in formulas with ALM implementation?
Hi @AashcaJ
Per the planual using select with versions is one of the few acceptable best practice uses.
It works fine in deployed models and ALM.
Andrew
select can be used on non production lists, list top levels, native versions and line items there is no issue with ALM.
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…
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…
