About AntonMineev

AntonMineev

Are P1 and P5 related hierarchies, composite directories? First, try opening your module and pivoting so that there are years, P1 level and other dimensions. If you have a sufficient calendar, then the line item for growth may already have the correct values. You just need to set up the correct view. If P1 and P5 are unrelated directories, then it makes sense to create a separate module and repeat the calculation.

AntonMineev

Can you show me "Applies to"? Based on the list of analysts and formulas you have written, you can get the correct numbers in the first line item for calculating growth. And for displaying on dashboards, use filters.

AntonMineev

Hi @Epratt! Are you clicking on an element in another module or are you copying / writing the formula by hand? This error occurs when the line item or module name is incorrectly described in the formula. Check if the specified element is in the SYS00 module. Do its names match?

AntonMineev

@Donna Marie, if my answer helped you please mark it as "solution". It helps to search for unanswered topics.

AntonMineev

Hi @Suman Reddy! Yes, you can change Number zero format:

AntonMineev

It's hard to say, I need a screenshot of the blueprint / module. It is likely that you can calculate the percentage of the increase in detailed measurements and put the summary = formula. Then subsidiary view will not be needed.

AntonMineev

Hi @JoannaAn! What formula do you want to write? And what will be the source and what will be the receiver? If you are going from P1 to P5, then you need LOOKUP. And if from P5 to P1, then the system will be able to add the data in the hierarchy itself (if your list if composite).

AntonMineev

Yes, there is currently no formula that returns the current day. The community has an idea about this, you can support it. In practice, we are doing an integration that loads the current date into the desired cell every day. If the accuracy of the calculation is not so important to you and there is no way to load the date, a good solution would be to use the formula from Chris below (with YEAR).

AntonMineev

Hi @algrigore! You can make formula "(Today Date - Birthday)/365"

AntonMineev

I ran into such a problem in the "Ideas Exchange" section. Only multiple page refreshes helped......

AntonMineev

No, I see links to update articles.

AntonMineev

I will add that the publication of a line item is done as follows:

AntonMineev

Hi @Donna Marie! 1. You need check that "total of all periods" is ON on Model Calendar/Time Range. 2. You need created a boolean LI and add formula "Amount'[SELECT: TIME.All Periods] <> 0" This is a valid scenario for using SELECT for filters. If your SKU list has a top level, then the formula should work without SELECT on the element "total SKU"

AntonMineev

Hi @tonybol! 1. Publish module with this list and boolean subset LI. 2. Make action "import in list" from this module. 3. Publish this action on UX. Thus, this action will update the directory subsets. The downside is that this button will need to be pressed to update subsets.

AntonMineev

@pdekas You would like to hide detail about VAT and summaries elements for other items? We can improve filter formula: The formulas and approaches themselves can be more complex, this is a simple example of a solution approach.

AntonMineev

Do not despair! Let's try to make a more complex filter: 1. You need a line item where you mark the elements that you want to hide (basic VAT elements). Put in front of them in manual TRUE. Select the type of summation ALL. 2. Create a line item from my last post (where all basic elements will be marked). 2. Create a line item for the filter. In it write a formula of the form "IF BASIC, THEN YOU ARE NOT OTHERWISE TRUTH" and summary methods FORMULA. UPD: Using the example, I realized that the summary methods in the second line item can be turned off.

AntonMineev

Hi @pdekas! If I understood the question correctly, then the simplest solution would be to apply a filter. If there are no other elements in this guide, then I usually make the line item "basic?" and put in the formula TRUE. And then I make a filter for "not equal to true". After, you will only see the summing elements.

AntonMineev

Good idea. I hope it will be implemented and the new modeling interface will be improved.

AntonMineev

Hi @Dominika_Dudzinska! Yes of course! The answer to your question does not depend on the type of interface. Both parameters are configured in line item format. P.S. This setting is available only to workspace administrators. The user cannot change the display options.

AntonMineev

Unfortunately, there is no simple formula. But you can export from native users list to an external setver and load properties from it into the module (use Anaplan Connect for make one process). This will copy the system properties. Since they are not mutable anyway. Alternative option: keep the list of users and properties in the data hub as a custom list. And already during the integration, you replenish the list of users in the model, as well as fill in the module with properties.

AntonMineev

In UX, you can publish "Field card". This will just be the line item for choosing a value and calculating the filter.

AntonMineev

Hi @Niraj.B! Usually, in this case, a line item is made with a choice of size for display (in a list format). Then the filter is calculated by the required rows (for example, their property must match the selected one). And this filter is applied on the page.

AntonMineev

Hi @lcapon! There are several reasons why data can be closed from editing: 1. They are calculated using the formula (as Rob wrote above). 2. This is aggregated data. 3. You do not have write access to the cell (governed by selective access, version settings, or dynamic cell access). 4. These are the actual months on the forecast version. To check the last point: see if there is a version in the module and if the switchover on. It is possible that you do not need it.

AntonMineev

Great news! Maybe someday we will see a similar post about native versions list 🙂

AntonMineev

You are welcome. if my answer helped you, please mark it as a solution.

AntonMineev

Hi @neg177! Do you use custom time or no? Classic solution with native time: 1. You calculate CB on month (OB + Movements). 2. You calculate Opening Balance use PREVIOUS(CB) formula. This formula take amount from previous month from needed LI.

AntonMineev

@dsoomar002 I'm surprised my formula didn't work. I specifically reproduced in my workspace and reviewed your video 🙂 Did the LI MAP work correctly? Is its format the same LI on which the SUM formula is written? In my example it didn’t work only then, the spell you have in the last module also has the same reference as in the example (in our example, LISS with number 4). I reviewed the video and there is no such thing. About SELECT/LOOKUP. We have two general problem for LOOKUP: 1. LOOKUP doesn’t work with summary “Formula” (SELECT works). 2. LOOKUP is not designed to work with the aggregate items on non-composite lists (lists with no parent hierarchy defined). (Copy from Anapedia). You can try SELECT, but since you can have hundreds of LIs, in theory you may need to choose a different non-list element instead of number 4. this story will not be flexible (PLANS).

AntonMineev

More complex workaround.....I have it, yes 🙂 You need LOOKUP with not-list elements. And I do this with SUM and TECH LISS: Let's go: 1. Make tech module with formulas: ISANCESTOR(Choose.Choose LI, ITEM(LISS)) and (WARNING) LI MAP = IF ISANCESTER? THEN AMOUNT.Amount ELSE BLANK. What is amount? It is a tech LISS with LI from your target module. 2. USE SUM FUNCTION in the target module: Source.Amount[SUM: TECH LISS Choose.MAP] You can see all in my screenshot. The basis of this chip is that we can use SUM together with LI that we summarize. P.S. If it helps you, give me Master Anaplanner 🙂

AntonMineev

Hi @dsoomar002! LOOKUP formula doesn't work with summary elements. You can make some option: 1. Change the formula in module A. Add + 0.000000001 there. And it won't be cumulative (or +0, but I don't remember if it works). 2. Remove the "Is summary" checkbox from LI Number 4 in Module A. Then it will not be a node in the subset. 3. More complex workarounds.

AntonMineev

Hi @Aditya1993! Are you confusing selective access and dynamic cell access? It is selective access that sets the rules for the reference within the entire model. In this case, it is the use of various dynamic cell access modules, instead of selective access, that will solve your problem. If for some reason it is difficult or impossible to change the access settings on the DCA, then you can consider a workaround through an alternative lists.