Best Of

This "Anaplan Formulas and Funtions" does not seem to be available in line with current L1 model training material from 2022.

Yeah.. definitely a limitation with report pages.

There's a way to do this, however it involves disabling the page context selector, and using the side panel to publish another card with the desired filtered context (text card is best), and then use this as the page context selector.

It isn't pretty, but it should work.

I am guessing you have selective access on the list, and your access is set to the Top level. Since the top level does not include these orphans, they are not shown in the module for you.

Depending on the scope you can just highlight and manually delete them, or you will have to give yourself selective access to the orphaned children in the list for them to show in the module.

Again depending on scope of the model and the frequency, I might look to change how this load happens, and first load to a staging area to validate the data is correct before pushing it to your list. That way it would catch in a list that might not have selective access on it which would be significantly easier to work with and safer so youre not adding failed list members to your list.

Hi @priyamshah -

Your understanding is correct, syncing the latest revision tag will take all of the cumulative changes from the previous sync and make them. In General, that is probably the outcome you are looking for.

The only scenario I can think of where you might want to run multiple back to back is the event when you need to Change an Input, or retain entered information. In this case, the Order of operations does matter in regards to the outcome. Example below.

Let say that I have a requirement to change my Input value to be at the lower level.

Here it is at the Parent Level:

Option 1: All changes in one Sync

Change 1: Update Formula to not look at Parent

Change 2: Update Input Value Line item dimension to match the rest of my data:

You can see here, the numbers all changed in the input which gives me different costs, which i dont want. This might then require an import or user intervention to correct data…

Option 2: Use a multi part Sync

I can Use ALM to my advantage here by doing a multiple part sync to retain the data.

Here i started with the first screenshot. I would simply create a new line here to take the data down a level. Since i havent changed anything else, I could sync this with no adverse effect.

Now I can re-write the formula for Cost to look at my new line item, and remove the formula from the new line.

I have successfully transformed the input without losing data or having to run import actions. There was also NO Downtime, or time when the data was incorrect.

As you can imagine in a small example like this, it might be silly to do this, but if you have thousands or millions of cells it can be a nice way to handle situations like this.

Hope this helps!

I would create a time range in the time settings that included all periods you are trying to calculate from and to. This will add those time periods to the superset of time in the model and make them appear in your calculation as valid time periods. You do not need to use this time range in ANY module or line item for it to work.