About DavidSmith

@Panji    Dynamic Cell Access is the answer This app and video tells you all you need to know https://community.anaplan.com/t5/Learning/Dynamic-Cell-Access-Learning-App/ba-p/33869   David ... View more

@Ari  This could be when you use on of the exceptions for list properties I'm not sure if it will work in this use case, but if you create list properties for one of the dimensions, you can choose to display them as well as the list name as part of the export   Alternatively, you may have to create a fake time list and map the data to that, specifically for the export   I hope that helps David ... View more

@rodriguezramiro  As you've found it doesn't work with page selectors, so the alternative is to publish a module (with the driver list), with no line items and use this as a selector module.     Guide the users to use that and then click the "open dashboard" button I hope this helps David ... View more

sorry for the confusion, I meant because it is repeated 3x in the formula, it should be split out into a single line item David ... View more

@michael_park  For performance, please split those component parts out into separate line items   Unique Employee.EmployeeName [ LOOKUP: Employee Name ] is repeated 3x   and you should split the parameters of the FINDITEM into separate line items too   David   ... View more

@Khanna  Thank you and I'm glad it helped. The most important thing you can do when starting out with Anaplan, is to think differently.  Anaplan is not like other tools or spreadsheets.  It has elements of those, but you shouldn't build Anaplan that way.  Leave the techniques you used in other products and try and understand multi-dimensionality Finally think about "what am I actually trying to solve", not "what did I do before" and that will help you   Oh, and read the Planual! https://community.anaplan.com/t5/Planual/ct-p/Planual   David ... View more

I think the INPERIOD() function will work for that. Or you could do a check using START() and END() David ... View more

@BahalR  One option you could try is to have a line item that is a a dependant drop down and a drive line item You could publish these two line items instead of a  page selector.  You should then be able to set up a filter on the displayed grid You would need to create a dummy list of SKU rolling up to Countries more details can be found here on how to set this up https://help.anaplan.com/anapedia/Content/Modeling/Build%20Models/Dropdowns/One-to-many_Filtered_Picklists.htm https://help.anaplan.com/anapedia/Content/Modeling/Build%20Models/Dropdowns/Many-to-many_Filtered_Picklists.htm   Alternatively, you could create a "SKU selector" module, which is synchronised, or filtered based on the country.  This could then by published to the side or top of the dashboard and then used to synchronise the bottom grid   I hope this helps David ... View more

@Asslam  This is quite a common requirement (new products, new headcount etc.) and as you've articulated it is tricky.   The best option (although manual), is as you outline, and change the code (and display name) of the dummy item to reflect the new item.  This might be OK on a small scale, but it could be quite a labour intensive task. Having two items (1 dummy and 1 real), might work in some cases, as you could map the dummy item to the new item, but you could end up with actuals on one item and forecast data on another   So, I solution I have often implemented is a combination of the two:   When you know the code and description of the new item, you map these to the dummy items in a module. Then for each data source (that is manually entered), you create an internal import to copy the data from the dummy items to their new counterpart. Once that is completed, you clear or delete the dummy item.   So it is a 4 step process 1. Update the list for the new items 2. Map the new items to the dummy items 3. Copy the data from the dummy items to the new items 4. Clear/Delete the dummy items   One word of caution.  If the dummy item forecast was driven from higher level attributes and assumptions, you will need to be mindful that the new item has the same attributes that pull from the higher level.  Otherwise, you may find you get a different forecast   I hope this helps David   ... View more

@VSekar  I am always very vary of users running actions during the planning cycle.  It is often possible, and better, to try and "model" the solution.  Many users running actions often is not going to create a good user experience due to the blocking nature of the imports So, in this case, if the values need to be "snapshotted" when completed, you could use a second staging module with logic tied to a "completed flag".  so, If completed? then data else 0 You can use DCA to control the setting and re-setting of the completed flags to ensure control throughout the process If you do need to run actions, you should look to created a saved views of the source using filters on those completed items and use that as the source.  It is critical (with all sources used for exports), that the views are as efficient as possible: use a single boolean per axis Only include the detailed values that are necessary etc. See the planual for more guidance on exports  https://community.anaplan.com/t5/Planual/ct-p/Planual   I hope this helps you consider any alternative to actions David ... View more

@Panji  to pull from modules with Time and Versions into a module without there are a few ways   Modules with versions. As with modules by time, you cannot SUM out of a module by Version and you also can't use LOOKUP, so you could use SELECT, but a better solution is to use the Current Version setting in the Versions tab.  this will return the values from the Current Version into the target module   Modules with Time You can use TIMESUM to pull all values from the module to the target.  This works for all formats and you can choose the Aggregation methods You can create a single dimensioned line item and store a time period you want to source, then use this as a LOOKUP.  If you have multiple years and want to pul the final value you can use SELECT[Time.All Periods] if this is turned on I hope this helps David ... View more