Platform

AntonMineev · ‎04-12-2019

Using the versions as a format will greatly simplify comparative reporting and open up new possibilities for modeling. The vast majority of system users would like to be able to analyze their versions (plan/fact, forecast/budget, comparison of different versions of the forecast/budget among themselves). To do this, they would be comfortable to choose the outgoing version and the version for comparison on dashboards. Unfortunately, in order to implement this functionality now you have to shift the data to a separate dimension (or lose flexibility). This not only takes up the cloud space, but also makes it very difficult to support the model. Emergence of new versions requires active intervention of Model Builder to support additional dimension. Many projects want to use an additional dimension right away, but this limits the detail of formulas by version and complicates the use of the switchover. This change will not only simplify model development/maintenance, but will also significantly improve the way Anaplan is perceived as a financial modeling and reporting analysis system (version and variance comparison). Please note this request (and the number of kudo for it) and add it to the roadmap. A large number of Model Builders will be grateful to you!

AntonMineev · ‎04-12-2019

It is important not only to sort, but also to be able to group the results in a multitude of measurements. In my country, most users are used to seeing the final elements from above. In Anaplan, it turns out that on single dimension tables, users see their usual results, but if several measurements are PIVOT, the order of the total changes and cannot be changed. This makes the experience very poor.

AntonMineev · ‎03-27-2019

This is indeed a very important request, as it will simplify many times the work of building Cash Flow reports based on line item subsets. When we need to take into account the correct formation of time and residues, and movements.

AntonMineev · ‎10-03-2018

Привет! Если стандартный механизм доступа не решает проблему, то можно использовать Dynamic Cell Access. Немножко теории от самого Anaplan: Anapedia , советы из Best Practices, обучающая моделька из AppHub . То есть создаеся отдельный модуль с LI Boolean с аналитиками Версии и ЦФО (и аналитикой Users, если требуется). LI "Запись": Если ЦФО немного и выбор хаотичный - тогда в ручную проставляете TRUE на срезе, который должен быть доступен на редактирование. Если подход системный - можно прописать формулу (например, смотреть на тип ЦФО или другое свойство). LI "Чтение": = TRUE Далее в нужных модулях проставьте данные LI как Read Access Driver и Write Access Driver. Примерно так: При значении на срезе FALSE в LI "Запись" пользователь не сможет изменить данные. Соответвенно, изменение значений на LI влияет на возможность записи.

AntonMineev · ‎10-02-2018

Hi, Ralf! You need to open the Users tab in model settings. Go to the Roles - Lists. Uncheck checkboxes on the necessary lists and user roles. This tab regulates the access to the change of the directory, and not to the input of data on its elements. I would leave access only for numbered lists that are at the mercy of users (for example, a list of contracts). Read more in Anapedia: King regards, Anton.

AntonMineev · ‎09-17-2018

Hi! I can offer you the following life: 1. Collect the data on line item with the versions (example: Source data); 2. For new Line Item write formula: Source data - Source data[SELECT: VERSIONS. Current Forecast]. As a result, the user will see the deviation between the selected version in the page and the current forecast. But there is an option without a select formula (And this is an interesting approach). Add Line Item without a version and subtract it from the source data. Anaplan works in such a way that there is no version on the position, then the data from the version that is marked as current is automatically taken. In this case, you will always have to subtract the current forecast data from the version selected by the user. The formula can look like this: Initial data (with versions) - Input data (without versions)

AntonMineev · ‎09-17-2018

Hi! Calculate the size of the model can be as follows: 1. Determine the dimension: multiply the number of elements by the measurements in the module. For example, there is a sales module. It contains data on 10 sellers for 12 months. Taking into account the element "Total year", the module size will be 130 cells; 2. Knowing the total number of potential cells, you can calculate the size of the model using the following formula: 1 billion cells occupy 7.45 gigabytes of cloud space. 2 billion will take 14.9 gigabytes and so on. It can be extremely difficult to estimate the dimensionality of the model, since the cells will occupy, among other things, the properties of directories, technical data, and so on. Try to estimate the length of the largest report that you plan to implement (for example, a P&L for 5,000 stores for 24 months for 30 articles in three versions (actual, forecast, budget) .This report will take 11 million 700 thousand cells taking into account the elements for the whole year).

AntonMineev · ‎09-17-2018

Hi, Greg! Usually, the data is duplicated if you have an "extra" analytics in the source module, for example, the version. If there is a version in the source, and there are no versions of the target module, then you get the sum of data for all versions on the target slice. As advised above, use specially saved view for this purpose (different filters, manual hiding, disabling of totals and so on). For example, a filter for the current version. This also can help not to increase the source module.

AntonMineev · ‎09-17-2018

Привет! Поставил "Kudo", надеюсь со временем исправят данную проблему. От себя могу предложить третий вариант обходного решения: Если эти агрегированные данные используются только в отчетах, то можно попробовать перекладывать эти данные через импорт (и повесить его на Action на дашборде), для чего потребуется в исходные модули добавить ссылку на мэппинг (см. скрин). Альтернативный вариант: не добавлять прямую ссылку на мэппинг, а заполнить его в ручную при импорте.

AntonMineev · ‎07-22-2018

Ksenia, а запись вебинара где-нибудь есть?

AntonMineev · ‎06-24-2018

Hi, anaplaners! Can you help me figure out the import of data into the module with frequent use of the list subsets? The module is P&L report, where each article is a separate Line Item. For each article, it is planned to assign its own subset of the list "Cost Centers" to optimize the place in the module. Also, subsets on articles are used for other lists used in the module. When I import data in mapping, all the used subsets appear. Unfortunately, I can not select the same column several times, so I have to choose "not applicable". As a consequence, the system does not load data into Line Item to which subsets are applied (although initially it is all the same lists). As a result, in order to correctly load data, you have to delete the subsets, download the data and copy the restrictions again. At the same time, the numbers do not change (all the elements are included in the required subsets), but they can not be downloaded at one time. I can somehow upload data to all line items, including line items with limited analytics in one action? Thank you!

AntonMineev · ‎06-21-2018

Это баг в серверной части. Я тоже столкнулся со следующей проблемой и написал в поддержку. Действительно, в некоторых моделях наблюдается такая проблема, что видно только одного пользователя. При этом в другом воркспейсе данный функционал работает правильно. Техподдержка ответила, что такая проблема есть и они работают над её решением. Ждем. Возможно поможет копирование модели и изменение её настроек.

AntonMineev · ‎04-24-2018

I managed to solve my problem using the approach of this article. the solution is based on the use of the summation method "Ratio": 1) Define the date hub fictitious elements through text formulas. When loading lists into the main model, set the property for the balanced element to 1; 2) Create a module for filtering. Lists we use the lower level of the composite list. In the module we add a Technical line item (always equal to 1, the summation method is a formula), and a line item for each level of the list that can be fictitious. Lists and name of these line items correspond to each level. 3) As values for these line item, enter any identical number (I chose 5) and multiply it by our property "Balancing" (1 or 0). Summation method: Ratio with settings previous level / technical position. 4) Use the filter on the lower level: hide the values that are not equal to the number indicated by us (5 in my example).

AntonMineev · ‎04-23-2018

Good afternoon! Tell me, please, how can I implement the calculation of a formula related to text functions with ITEM on a node element? The problem is this: 1)Data HUB was configured, which forms balanced hierarchies (in accordance with the course 305 and this topic in the community ). 2) In the basic model it was possible to generate a directory having a lot of balancing levels (See Screenshot): 3) This was our goal, but for the convenience of users it would be desirable to hide the balancing levels, that is, to get such a view of the table: A solution is needed that would be able to hide these levels automatically - a filter (in the example above it is hidden in the manual). However, when configuring a filter, I can only use modules that have the same change and at the same level as the original module (in my case it's level 8). But I can not select the L8 layer in the module and set the values on the nodes that could identify fictitious nodes. Different formulas and their combinations that can determine them can not work with the summation type "formula" (because they use ITEM or LOOKUP). To use properties of other levels too it is impossible (an error: different directories / levels). There was another "manual" version using the "Select Item To Show" and searching for balancing elements by code. But this function has a limit on the number of values and does not allow me to save my choice: What other approaches can be used to hide the balancing levels of a balanced hierarchy? Thank you!

AntonMineev · ‎03-22-2018

Добрый день! Мы бы с коллегами очень хотели поучаствовать в вебинаре, разбирающим особенности действия Model Builder клиента при смене бюджетного года и какие технические подходы есть к архивации бюджетных данных. Например, как сохранить архивную версию бюджета, чтобы данные на ней не зависили от изменения модели, но при этом были оперативно доступны для просмотра.

Platform

Academy

Master Anaplanner

Programs

About AntonMineev