Hello All, if someone could walk me through the below step by step because I am little bit confused
Hi @omarismailcch1
When you enter blueprint mode of each module there are common elements which you can configure including the "Summary". This is what dictate the aggregation behavior for the dimensions applied to that line item.
The instruction is indicating that you should update the Summary method from None to Any. This means that if ANY month is an actual period, than the quarter & year would also be marked TRUE as these are the summary roll up points.
To complete this activity, within each line item click the ellipse with the summary method column (see yellow highlight below):
You are then able to update the summary method for the line item:
@tifashen888 Thank a lot Tiffany, this is really informative , I did what you told me but the outcome is not the same as what Anaplan example looks like.
this is my blueprint view and final outcome
And this is final outcome form Anaplan
HiΒ @omarismailcch1
To understand why you may be receiving a different outcome, I'd suggest you familiarize yourself with this function: https://help.anaplan.com/currentperiodstart-a7af7113-e1dc-478d-bbbe-ecb597092991 . It would appear you may have missed a step in defining model calendar.
You need to set the current period first in the module calendar
The function CURRENTPERIODSTART picks the current period from the model calendar itself.
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β¦
