About DmitrySorokin

DmitrySorokin · ‎07-05-2021

We are experiencing the slow adoption of new UX because of this feature gap. Wondering how far down is it on a roadmap? @Miran how much more support is needed for the next steps?

DmitrySorokin · ‎12-26-2020

Multi-select is asked by every Anaplan customer I worked with. Workarounds are available but they are not perfect and end up impacting user experience.

DmitrySorokin · ‎11-12-2020

Perhaps, it is worth adding that import also breaks when mapped line items have a dimension replaced with their respective subsets. When source module still uses 'full' dimension, but line items had a change in applies to from dimension to subset, we will need to readjust the import. Imports also break when filter that applies for a source view had a dimension changed from ‘full’ to a subset.

DmitrySorokin · ‎10-19-2020

Thanks for the article @paul.rosal. I will leverage your post to share some learnings as well. We expireinced some data loss issues when using module to module import in the Target module. Mostly because of not fully understanding the default settings of "Clear target prior to import" in the settings of the import action. Module to module import is a two step process: 1. Clear the target 2. Import values from source to target The issue we are seeing in all our imports, is that Step 1 "Clear the target" is clearing more values than we intent to import. After a few hours of troubleshooting we now fully understand the behavior, which is best explained by your example where you set source line items to No Data. When Source Line Items are set to No Data, no values are actually imported, hence the dialog message after the import shows that nothing is updated. The reason values are cleared, is because Anaplan finds Matches between Source view and the Target module and Clears them as part of the Step 1 of the module to module import. This is also true in your other example, when we create a custom action to import Blanks (for lists and time) or '0' (for numbers), Anaplan first Clears values for us, and then imports Blanks and '0' where we ask it to import. The dialog message after the import will show us how many items were imported, but it won't tell us how many were cleared as part of Step 1. This creates confusion when we see more data is cleared, than we actually intent to set to Blank or '0'. There is an article explaining this behavior, however, I thought the above learnings will still be valuable to share with the group. https://help.anaplan.com/anapedia/Content/Import_and_Export/Import_Data_into_Models/Clear_the_Target_for_a_Module_Import.html

DmitrySorokin · ‎09-25-2020

Yes @khooton , this would be good. Juggling the workspaces around is one of our regular activities.

DmitrySorokin · ‎09-02-2020

This will be helpful for us as well, as we need daily size tracking of our models and workspace usage - this is all to make sure we don't hit the limit during our nightly batch process which results in holding all the jobs. Wondering if are able to send an API request to get the model sizes on demand and automatically.

DmitrySorokin · ‎09-02-2020

This will be helpful for us as well, as we need daily size tracking of our models and workspace usage - this is all to make sure we don't hit the limit during our nightly batch process which results in holding all the jobs..

DmitrySorokin · ‎06-23-2020

There are couple examples of this to be useful for us. 1) If model is pre-loaded into the memory then the nightly batch process can start processing data immediately. Currently we are waiting for 5-10-15 min while model is being loaded. Which may happen multiple times during the batch cycle as we have longer than 60min of waiting between certain scheduled data feeds. 2) Our users are in the models during the day, but out for lunch at noon. This means the first user in the morning or after lunch waits while models are loaded, leading to down time in their workflow.

DmitrySorokin · ‎05-31-2020

Great job @serena.zhang. Very inspiring .

DmitrySorokin · ‎05-02-2020

Very much required functionality.

DmitrySorokin · ‎05-02-2020

+1, experiencing the same issue.

DmitrySorokin · ‎01-04-2019

Thanks David, I definitely learned from your post. Dmitry

DmitrySorokin · ‎01-03-2019

Hi NicolasCadier, If you are trying to delete items in Model B with the selection stored in Model A, then you could import the boolean line item into model B first and then use 'delete using selection' to clear list items in Model B. Is that what you are trying? There is no way you can delete items in model B from any action located in model A. The only way is to go to model B and delete items from there. Dmitry

DmitrySorokin · ‎12-31-2018

Hi NicolasCadier, It is not possible to reference lists between the models, you have to import them to each model via actions. A good way to export lists from a model (data hub model for example) is to first create a module (hierarchy management module), where you have line item for each list you are planning to export. Each line item is formated as the list you have in mind. Once that is done, you can create a view for each list and then create an action in other models to import from that view. It is a better way, because in views you can turn off the summary level (or top level), which is not possible when you import from the list directly. In this way, when import action is run, you will have all green checks, which gives a lot of comfort that all data is imported succesfullly. Hope it helps, Dmitry

DmitrySorokin · ‎12-31-2018

Hi Dahya, I am not sure if there is a way to create list members based on formula. In Anaplan you can create list members by importing data or mannually populating. You could create the logic you described in Excel - populate list with member 1 to 1000. And then import or copy paste them to Anaplan. Dmitry

DmitrySorokin · ‎12-28-2018

Hi manuebilly, I don't like too many nested if statments either. My preference would be to use mapping instead of formula. I would create a list "age list" of values from 1 to 100 (or whatever is reasonalble) and then create a property Bracket formated as list Age Bracket. Then mannually map every age value to the Age Bracket list - only takes one time. In your module you already have 2 line items age (as number) and age bracket (as list) I would create one more line item: age list = finditem(age list, text(age)) and then use formula in your age bracket line item: Age Bracket = age list.Bracket [lookup: age list] You will have blanks for all values above 100, so I would adjust formula like this: Age Bracket = if isblank( list.Bracket [lookup: age list] ) then "above 100" else list.Bracket [lookup: age list]. Hope that helps, Dmitry

DmitrySorokin · ‎12-07-2018

Hi pvijayateja, 1. Views do not take up extra space. Only modules do. You could see the number of Cells that moudles take up within each Model. The biggest one are easy to identify and usually they have too many dimensions to allow all sorts of slices for the user. I try to keep number of dimensions in the module to maximum three or four including time and versions. 2. The only way to know which dashboards are using the view is to have a very good description for your view, something like: Headcount View for CFO Dashboard. However, keep in mind that over time, CFO Dashboard maybe renamed to Exec Dashboard which is a problem. 3. If you delete the view, it is NOT going to disappear from the dashboard. However, you won't be able to publish that exact view again to other dashboard unless you re-create it again. What is important though, if you delete the view that was used for any of your export actions, then your action will not work again, it won't find the source of data. So you will have to 'record' that action again. You can review which views are used for any of the actions within your model by going to Model Settings-> Actions-> Imports and look over Source Object column. Keep in mind, that there maybe other Models that use the View and you won't find out unless you remember. That is why it is important to have a well descriptive name for your views with info where they are used. Thanks and let me know if that helps, Dmitry

DmitrySorokin · ‎12-06-2018

Assuming you have Module A with dimensions Employee and Time, and Module B with dimensions Shop Number and Time. For the new line item "B. H ours W okred in a Shop" Could you try formula: B.Hours Wokred in a Shop = A.hours worked [sum: A.Shop Number].