About M.Kierepka

M.Kierepka

Hi @PoojaGupta, Yes, you need to input this as data (it is used to check if your model is working as expected).

M.Kierepka

Just try to run the actions/processes - by default it should work. Otherwise, if it won't pass, that means that your system/VPN administrator blocks this traffic - you need to contact them and give them link to Anaplan documentation, they will know how to do it.

M.Kierepka

Hi, I am still sure that it can be done in nice and clean way (0 maintenance cost!), so I prepared small demo: @alexpavelI think you slightly misunderstood me: I proposed to use filter to show only 2022 (or generally current year periods), but to also use hide/show to only show one column for properties, but multiple for Value. How it looks like: NUX (using custom views and just-released ability to Show/Hide there on nested dimensions): Classic UX: @AlexGSGInstructions how to do it (I am also attaching a video with walkthrough of the 3rd point): 1. Blueprint of main model: 2. Blueprint of the filter that needs to be applied to view to get desired results (I assume you already have some other line item that determines what is current year that should be shown, per your needs): 3. Then, when you are building the view in NUX, apply filter, and then: HOLDING CTRL KEY click on "All Periods" (lower columns header row) for all properties columns and on "Value" (upper columns header row), then right-click and select option "Show->Selected". We are almost there -the only other thing you need to do is to hide "All periods" for "Value" line item: right-click at it and select option "Hide->Selected".

M.Kierepka

Well, they definitely have as it is information stored somewhere on the serve, but Anaplan doesn't charge customers for that. It's also probably not that much space, as it's just config information, definitions, comments etc. The same applies to things like My Pages, space consumed by Tenant configuration or tasks definitions in Cloudworks.

M.Kierepka

Wow, I really appreciate all the work you have done! I downloaded it from Mozilla's page, tested briefly, works like charm I think more and more Anaplanners use New Modelling Experience (including myself), but still thank you for supporting old one.

M.Kierepka

Hi @selvaam12, Firstly build the module just with the base values, so base dimensions + Time + line items (Sales, COGS, Profit). Then create line item subset for this module and add these 3 line items to it. Next, you need to create CALCulation module, where you have all base dimensions + Line Item Subset + just one line item (can be called 'Values'). And the last step is to create your reporting module, just as you want, with all base dimensions + Line Item Subset + 3 line items (CYTD, PYTD, %Change), with respective formulas that will use your CALC module, like this: CYTD=TIMESUM(CALC.Values, SYS.CY Start Month, SYS.CY Current Month) PYTD=TIMESUM(CALC.Values, SYS.PY Start Month, SYS.PY Current Month) % Change = (CYTD - PYTD)/PYTD

M.Kierepka

Hi, If you really want to use line items as periods, and later map it to Time dimension, create Line Item Subset, add your "months" line items to it, and then in new module you can collect it and map to Time dimension. But I'd firstly ask myself a question, if this architecture won't be too complicated and hard to maintain - maybe it would be easier to define three line items: Department, Country and Values, where all have dimension of rows, but Values also have dimension of Time, the same as whole module. Then you can have two dimensions in columns (Line Items and Time) and filter it/select in a way that you only select one occurrence of first two (properties) line items, but show full year for Values.

M.Kierepka

Hi @zaibhamid81, Go to Apps section, in the right-upper corner you should see a blue "Create an app" button. If you don't see it, please contact your training coordinator and tell them you need to be given "Page Builder" access, as currently you are unable to build in New UX.

M.Kierepka

Hi @zaibhamid81, I think it is because you have Dynamic Cell Access enabled for this line item, and value of access driver is "False" - that's why you can't see it. If you want to see all values, go to Blueprint and clear relevant fields (note: it was probably put there on purpose, so you need to be sure that you are not removing some security from the model).

M.Kierepka

Can you give more information or screenshots of blueprints/examples? I'd say use LOOKUP to map Time and "dummy time" list if you have such, but more information is required to help you.

M.Kierepka

So in "SYS Unit" just add "Parent Building" line item, with format of Building and formula as "PARENT(ITEM(Unit))". In Module 1 add new line item (let's call it "Multiple?"), format: Boolean, summary: Any, formula: ISNOTBLANK(LEAD_ID) AND LEAD_ID <> LEAD_ID[LOOKUP:'SYS Unit'.'Parent Building']. Example (I placed Parent in the same module for simplicity and clarity): Blueprint (notice that LEAD_ID is text, but can have format of any list and this should still work):

M.Kierepka

Hi, Easiest solution I can think of (based on your screenshot, I assume your LEAD_ID line item has summary:Last Non-Blank enabled, if not, enabe it), I also assume that your L2 list has SYS module with line item "Parent", which for each L2 item gives their L1 parent (if not, make such): Add new line item, format: Boolean, summary: Any, formula: ISNOTBLANK(LEAD_ID) AND LEAD_ID <> LEAD_ID[LOOKUP:SYS.Parent] Because summary is Any, it will give you TRUE at L1 level if there are at least 2 different IDs.

M.Kierepka

Hi, Yes, it's possible - all you need to do is to create filter line item (probably in SYS module), format Boolean, which will only show such >0 rows, and use it as filter in your module (can be saved view or custom view in New UX). You will need also helper line item to determine which year is current year, like SYS.Current Year formatted as Year (no dimensions) and with formula: "PERIOD(CURRENTPERIODSTART())". In the formula of the filter line item (dimensions of locations is needed here) you need to write something like this: "Value[LOOKUP:SYS.Current Year] > 0". Exact formula depends on what should be taken as current year (above option works if you want to use "Current Period" setting in Time tab , but you can also make it work with some line item in SYS module, where you would pick which Year you consider as current).

M.Kierepka

Hi, I assume Employee_number and Manager_number columns have "Employee" list format (if not, use FINDITEM and produce such columns). Then: 1. Add line item "F_TRUE" with format as Boolean and formula as "TRUE". 2. Add line item "IS Manager?" with format Boolean and formula: 'F_TRUE'[ANY:'Manager_number']. This is your result - it will indicate if this employee is in manager column anywhere on this list.

M.Kierepka

嗨@Vikas7895,你会发现在这个articl回答e. Most important part: Why should hierarchies not be in the data hub? To answer that question, you need to understand why hierarchies are used in the first place. Essentially, hierarchies are only needed to aggregate data for analytical purposes, and since users will not normally login to the data hub, the lists essentially take up space. With that said, it is perfectly okay to create the hierarchies for testing purposes to ensure your actions from the meta modules are building the hierarchies correctly, but as soon as the actions are working correctly and have been verified, you can remove the list structures from the data hub. A case can be made that certain implementations may need the hierarchies created in the data hub for validation purposes of several sources. If this is the case in your implementation, just be sure to only use the hierarchies for validation purposes. In addition to the above, there are two more reasons to not have hierarchies built in the data hub—cluttered data, and spoke models that pull data from the lists. Data hubs need to be clean and clutter free to ensure optimal performance, which also makes it easier for the administrators to understand exactly what data is stored in the data hub. Additionally, when you have lists—especially hierarchical lists—spoke model builders will sometimes build their lists from the lists within the data hub instead of from a view. It is best practice to always build lists from views from within a module so the action can benefit from filters (there are no filters when importing from lists).

M.Kierepka

Hi, It looks like you have extra "%" there - I believe it should be "set Command=.\AnaplanClient.bat %Credentials% -workspace %WorkspaceId% -model %ModelId% %Operation%" instead of "set Command=.\AnaplanClient.bat %Credentials% -workspace %WorkspaceId% -model% %ModelId% %Operation%" Also, if you are posting code to community, I recommend putting it in "Code sample" type of input: @Echo off set AnaplanUser="Anaplan.User@anaplan.com:Password" set WorkspaceId="8a1234567897c12b014bf01234567890" set ModelID="CD1234D60CA84E9A123C1C5D061C1234" set Operation=-service "https://api.anaplan.com" -auth "https://auth.anaplan.com" -export "Employee by Department.xls" -execute -get "C:\Employee.xls" rem *** End of settings - Do not edit below this line *** setlocal enableextensions enabledelayedexpansion || exit /b 1 cd %~dp0 if not %AnaplanUser% == "" set Credentials=-user %AnaplanUser% set Command=.\AnaplanClient.bat %Credentials% -workspace %WorkspaceId% -model %ModelId% %Operation% @echo %Command% cmd /c %Command% pause

M.Kierepka

Hi, It's weird, because exporting Management Reporting pages with pictures to PDF works for me. Maybe it's about links - I am using links that don't require login/authorization to view, if you are using some protected repository, that might be different.

M.Kierepka

Hi, Tabulation is limited only to few levels, and there is no easy fix for that (both .xlsx and .xls share the same settings). So to distinguish levels:

M.Kierepka

你好,1。假的区别是给你的东西u a rough estimate of how many months has passed - it's just working on the assumption that on average a month has 30 days, and we round it down to whole numbers, so it represents only full months. You can say it's heuristic, and even better one would be if you change 30 to 30.5. 2. Then, in Full Months Difference I use that rough estimation as base, but check if it's really correct, and if not, try to fix it by adding or subtracting one month, and again checking if maybe now it's right. That's because in Anaplan we can only estimate the difference in months, but we can precisely check if this value is correct.

M.Kierepka

Thank you for additional information. As I understand, the problem lays in Anaplan process in mapping items between full and subset list on-the-fly in LOOKUP - as you pointed out, it doesn't work as expected (but in the same time it doesn't throw error about incorrect dimensions during development). Maybe you can report it as a bug and Anaplan developers will fix it? In the meantime, I'd advise using this extra line item, as you did (however I'd place it in System "Param Version" module and remove all unnecessary dimensions).

M.Kierepka

Hi, Based on the fact hat you use LOOKUP, I assume your versions list is some custom one, not default Anaplan Versions? (As you cannot use lookup with built-in ones). Can you provide screenshot of blueprint? Maybe you have some difference in dimensions used?

M.Kierepka

Hi, There are few options, you should choose one that fits you best - and it depends on what you exactly want to accomplish: 1. Add Users dimension to import module. Then in import definition, add "Ask each time import is run" for Users dimension. This will mean that each user will have a separate view. 2. Create dummy users list, then do the same as above. This is harder to build, but allows for more flexible access management (e.g., hierarchy of users, managers can see what other people imported based on your needs). 3. Depending on how your module is defined, you can tweak DCA in a way that, depending on a user, they can read/write data to specific lines.

M.Kierepka

嗨@GeorgeDuckett,哇,真的很好!好有趣的ctionalities, extremely helpful, and at least for now I have not met any bugs. Idea from me: Thanks to formula autocompletion and function information, it's fantastic when you don't remember order of arguments or how some function should be used. And in my opinion, all would benefit even more if you could add: “Be cautious” — warning, maybe in form of underline (not red, but yellow/orange), for functions like TEXTLIST, RANK, SELECT:, FINDITEM, to warn users that function like this can cause performance or maintenance problems. “More info” — just like you have link to the Anapedia page for highlighted function, maybe you can add some link to Planual about it? (TBH, such links should be added by Anaplan to Anapledia for some functions like SELECT: or TEXTLIST…) Also, as you released extension for Chrome, it should work and be installable on any browser that use Blink browser engine (so not only Google Chrome, but also Microsoft Edge, Vivaldi and Opera). However, I am using Mozilla Firefox, which uses different engine, but still your extensions should work there, even though currently it cannot be installed, as it's not in official Mozilla Firefox addons store. So I am using developer mode for your plugin, and tried to adapt it, so it can work under Firefox, and… it worked. So I'd be really happy if you could also officially release your plugin for Firefox, so others can use it as well - the only thing I needed to adjust is manifest.json (I am pasting content of the one that worked for me, feel free to change/update it): { "browser_specific_settings": { "gecko": { "id": "georgeduckett@anaplan.com", "strict_min_version": "90.0" } }, "content_scripts": [ { "all_frames": true, "js": [ "/dist/content-script.js" ], "matches": [ "https://*.app.anaplan.com/*" ], "run_at": "document_end" } ], "description": "This extension enhances Anaplan formula editing in several ways; providing code completion, hover info and validity checks.", "icons": { "128": "logo.drawio.png" }, "manifest_version": 2, "name": "Better Formula Editor for Anaplan", "version": "1.1.0", "web_accessible_resources": ["dist/*"] }

M.Kierepka

Hi @zhaotun1, Unfortunatelly not, at least not identical layout. To do something like this, you can create bar chart (and users can toogle between Value and % using selector):

M.Kierepka

Hi @sosunkwo, The answer greatly depends on how you define this difference. Using your 3 examples, I tried to produce something that might be close (with more examples covering edge cases): Blueprint:

M.Kierepka

Hi, If you are talking about formula indentation, it is coming soon according to February sneak peek: https://community.anaplan.com/t5/Releases/February-sneak-peak/ba-p/131359#toc-hId-809408774 And I hope more and more improvements to Modeling Experience are coming, like formula autocompletion, syntax pre-checker etc.

M.Kierepka

Hi, Please look at this "How To" article, I believe it is exactly what you want: https://community.anaplan.com/t5/How-To/Seasonality-Chart-Simple-as-That/ta-p/119504

M.Kierepka

Hi, Currently, there is no way to do that - the only thing you can do to "save" the structure of your model is to export definitions of line items, lists etc.

M.Kierepka

It's because your Target Calendar doesn't have source period in it. This means there is no one-line solution, but let me give you two alternative solutions (either 1 or 2 will do the work): Please note that you might already have "Calc_2" in some time settings SYS module (if not, build it there), and can utilize it here and in the future in multiple modules.

M.Kierepka

It's just miscommunication - I thought "Custom Calendar" is some list you created with different time structure than default Anaplan Calendar. But your "Custom Calendar" is just Time Range - Anaplan shouldn't have problems with mapping values between them. About solution: In target line item, put formula "LAG( Module A.Sales, 24, 0)" Explanation: LAG allows you to bring values with offset in time. 24 is the number of months between source and target (I assume you want to always pick numbers from "current year minus two"). The third argument, 0, tells Anaplan what to do if it will try to get values outside the range. More about LAG formula: https://help.anaplan.com/3064919f-964e-4b84-be56-15f0e127e371-LAG