About nathan_rudman

nathan_rudman

no, this endpoint doesn't exist. The only additional information you can get is by creating exports, which become API endpoints.

nathan_rudman

not clear what you mean by previous SKU but I think the right formula is RANKCUMULATE as cumulate only cumulate in the order of the list, not the ranking you provide

nathan_rudman

we were all surprised when we discovered how hard it is to get there. will use this thread to feedback the UX team

nathan_rudman

I don't think it is possible from the UX. From the API you can do it, as the files are an available endpoint. You can use Anaplan Connect, or third party like postman or anaplus.app can do that

nathan_rudman

you should be able to see the ALM sync event in the history. if you roll back before you'll loose the ALM sync. if not you should be fine.

nathan_rudman

I noticed sometimes there is a delay betwen your input and the action.

nathan_rudman

time is the only solution to avoid the circular reference. What avander and Yelena expose here only allow you to bring 1 previous value. We use Yelena's solution often enough (especially for list settings such as brackets with lower- upper bounds), it takes 2 minutes to set up, but it's not replacing previous.

nathan_rudman

historical or a driver collected by finance from business for the split between the two historical you can also compare against the driver an see if it makes sense.

nathan_rudman

assembly config is your list where you are writing this formula ? in your list you should have a property that's the parent of the list itself and that's your grouping. Else you can use Assembly_Item ps:try not to do formulas inside rank, it's bad for performance ps2: our best practices say these formulas should be done in a module: gives you more flexibility

nathan_rudman

This is simply the rank formula with a grouping using a parent formatted line item

nathan_rudman

this is a weird behavior but it's been like that for a long time. In a model, you can create and load from a file items with the same name and code as a parent, but if you import it from your DH it fails.

nathan_rudman

x100 ? 🙂

nathan_rudman

I had that same issue it was because of my screen resolution that wasn't "standard ratio" (was using a TV). On my laptop screen it worked fine.

nathan_rudman

you need to sum on the meeting mapping of your source module (and product, I think you should add that dimension to your LI item so it is the same as your module)

nathan_rudman

the reason behind the fee, beside the power you get access to, is that hyper models need a specific hardware

nathan_rudman

what if you don't select % but rather number (mans you have to divide by 100) and put the % in the suffix ?

nathan_rudman

You are summing by product which seems un-necessary as you have products in all source modules. However if module 1 is the source, you don't have entity here so you'd need to SUM of an entity property (individual can be mapped to entity maybe ?)

nathan_rudman

unless you are very short on space, a few milion cells really don't matter

nathan_rudman

Due to the nature of Anaplan (live calc), in any finance model, it is essential to have a snapshoting system to copy the values of versions into a module were these valus will not change. Typically, I'll have a snapshot module with the important dimensions (Cost center, accounts, time etc) and a "snapshot version". Once you have done your forecast, you copy the results of it into that module.This way, the chances for the numbers to change are very limited (only deleting list items will have an effect). Your final reporting should then be a mix of the native versions where you do the calcs and these native versions.

nathan_rudman

I personally prefer to store data in a dimensional way, not transactional, I think that is just easier to use in Anaplan. That means solution one. You don't need to update price every month. You can create a logic with a line item "Final Price" that take previous price unless the line Item "Price Change" is updated. And you can add another LI called "Price Change Date" to specify a particular date within the month. This way you only need to update if there is a change, otherwise price is carried forward.

nathan_rudman

yes you can export model history and re-import it into Anaplan for example for analyses. It can be automated via AC or any other integration tool.

nathan_rudman

Usually, user access is managed via several imports: 1: import the user name/role/SSO 2: reset the existing selective access 3: set new selective access 2 is quite difficult, because to reset you have to import the codes they have access to in the "None" column of that dimension. So if you really want to do that, you need to import into your user management what they have access to currently, use it to reset their access and then import a new one. An easy way for this is to reset their access via changing their role to "No Access". This will remove any SA they have. However it will kick the user out of the model if they are in when you run the process AND erase any data they might have input on the user dimension

nathan_rudman

You can use a specific behavior of Anaplan: - put the dimensions you want the users to select as dimension of the data module (cost center, time whatever) - for all line items in this module, remove these dimensions (it will create subsidiary views) - create a "filter" boolean line item with the default dimensions of the module - make a formula that's TRUE when the data is equal to the diemsnion ITEM(Dimension) - display the module of a dashboard by filtering on that filter line item - you module is going to sync with the dimensions selected by the user and be in sync

nathan_rudman

why would you need an assign action ? and a clear ? built user management many many times and never used those

nathan_rudman

that's the game of community 🙂 been away for a while, very busy times. I'll be back as he said !

nathan_rudman

In your source module, where you have the data, you need to create a mapping line item formatted as List Account. You make a formula to map it based on the numbering of the account item. You can then SUM the values by that line item in your target module which has Account as a list.

nathan_rudman · ‎08-14-2020

Hi Camille, When you reference the User list as a source, you need to have a LOOKUP with a clear mapping on which user it will look up. Otherwise Anaplan does not know how to link your target with the user list and tries to take the total level, which doesn't exist. you can usually do this mapping easily in a module on your "fake" user llist and doing a FINDITEM(Users,email)

nathan_rudman · ‎08-14-2020

It depends the context: a one time thing or a functionalities used by user recurrently ? one time thing: - clear one of the list that is driving the module - set the line items to no data and back to their original format recurrent: - you need a module with similar dimensions and a line item in "No Data" format. You can then import from that module into the oe you want to clear. Publish that as an action and make it available to users

nathan_rudman · ‎08-11-2020

I think the term you use as calculation wave is what jared refers as the algorithm that opens the model. In which case yes the "order" and references has a lot of importance, as stated in the planual rule don't daisy chain. Recently I worked on optimizing a model with 12K+ line items and the impact of small calculations can be important in the end depending where they are in the calculation chain.

nathan_rudman · ‎08-10-2020

very often the DH is used to control the validity of data. How can you control the validity of data without hierarchies ? No user I know can. Also the DH should be the place where subsets are created/maintained. Very often on a COA or list of cost center,you'll need a hierarchy to be able to properly define a subset (is this account revenue, is this cost center profit center etc)

Online Status	Offline
Date Last Visited	Thursday