Hi David, The term "match on names or codes" on your "L6, L7 Customer, Product #" tab really means "attempt to match items automatically", as opposed to the second radio button where you manually map items. Manual mapping only works in smaller lists and for line items where you know that they're never going to change from one day to the next. (E.g. the "UNITS_VOLUME" line item in your source module gets manually mapped to the "Units" line item in your target module or something like that.) I usually recommend that you only map things manually if you need to. If you create new line items in your sources or targets it could throw the import out of whack unless you go in, edit that import from the Actions tab of the gear, and explicitly tell it now to ignore the given new line item. (For this reason you should always import from a filtered saved view, never directly from a module, so new things don't pop up and confuse the import.) More broadly, pushing numbered lists across models requires some special care because the true technical ID of the member in your source usually won't match the true technical ID in the target. Suppose you have a Product list with 5,000 products in it. Product "Chocolate bar 200 g" in both of your models might have a code of 12555 and a display name of "Chocolate bar 200 g". They LOOK the same. But in the data hub that was the thousandth member created in that list, so its actual true technical code is #1000. But in your sales planning model you created that one early on as a test product, so its true code is #6. You therefore cannot map automatically because the codes differ. The safest thing to do is to ensure that your source module has a line item called something like "Product Code" which is formatted as type TEXT and has a formula of CODE(Item(Product)). Here our chocolate will show up as 12555. Then on the main mapping screen you tell the import that this column corresponds to your target's code. Basically you want to ignore the #6 and #1000 altogether. Does that make sense?
... View more
As David mentioned, if the data set is small then exporting the relevant data to CSV and manually updating and then re-importing would probably be easiest. But for larger data sets creative use of time ranges might be an option. Time ranges are totally independent of the time dimension, they are awesome, I use them all the time (no pun intended). One approach could be the following: 1. Create a time range called FY18 Only. Set the period to FY18, with just 1 period, no aggregations needed. 2. Identify the modules that contain blue-cell data that you want to shift forward. Suppose you have one called "My Data Module". In Blueprint view in the module, change the "Time Range" setting from Model Calendar to your new "FY18 Only" range. Note that you will need to do this for all line items in the module (copy/paste). You have now effectively frozen this module to only have 2018 irrespective of what the current fiscal year is. 3. Change the current fiscal year in the main time dimension to FY19. 4. Copy your module, call the copy "My Data Module Temp". 5. In "My Data Module Temp", change every line item's time range setting back to Model Calendar. Now it will have Jan-Dec 2019 with empty cells. 6. In "My Data Module Temp", create a line item called Prior Year Month that is formatted as a time period. The formula for this line item becomes ITEM(Time) - 12. 7. In "My Data Module Temp", make every line item a formula that points to "My Data Module" but uses a lookup on your new Prior Year Month line item. So the line item in "My Data Module Temp" called 'Cash and Cash Equivalents' which used to be blue cells would become My Data Module.'Cash and Cash Equivalents'[LOOKUP: Prior Year Month] 8. Copy/paste this formula across all line items so eventually every line item is a formula that is looking back a year. Now your temp module is filled with formulas and black cells of data. 9. Delete all of your new formulas in "My Data Module Temp". In doing so, the results of those formulas will remain, similar to Excel's copy/paste-special-values. Now you have all blue cells of data but shifted forward 12 months. 10. Go back to "My Data Module" and change the time setting back to Model Calendar instead of the FY18 Only time range. This blitzes the data and it is now empty. 11. In "My Data Module", select Data > Import, Connect to Anaplan Model. Navigate to your temp module and re-import your data 1 for 1. 12. Delete "My Data Module Temp". Time ranges are also great for archiving old data that you don't need to have throughout your entire model. For example, they work well if you have one consolidated report module that you want to save five years of history for but don't need that history elsewhere, create a time range for it.
... View more