Hi What are the different formulae for each version that you are trying to create? Could you include some screen shots? David ... View more

Hi David Yes, Wk53 FY16 will be missing so those values will fail and will need to be incorporated into FY16 I'm glad the suggestion was helpful, even if time consuming! David ... View more

Hi David I’m assuming that the data in Wk 53 FY16 will need to be mapped (to Wk52 FY16 or Wk1 FY17). If so that causes a problem when trying to map model to model, because you can’t manually map time:time.    So I think an export/import is the only solution:   For each data module: Export the data to .csv Find and Replace "Week 53 - FY16" to whatever the new week is Create an import from the file back into the module Once done for all modules, copy and archive the model (just in case!) and  change the timescale Then for each module run the import from the text file   If you need to apportion Wk53 – FY16 (e.g. split the value into Wk52  FY16 AND Wk1 FY17) that will require some additional logic Create some additional modules (for each data source) to calculate the split of Week 53.  This will need to include the new aggregated values for the weeks either side of Week 53.  I would create line items with the labels for the target weeks Export the data for the split Create an import Export the data from the original module as above Create the import as above Copy and Archive the model, c hange the timescale and run the imports from the original modules; Week 53 – FY16 doesn’t exist in the new timescale so the original data won’t come in Then run in the data from the “split” export files and it will overwrite the original weeks that are part of the apportionment and replace them with the new value incorporating Week 53   I hope this helps. David ... View more

Another solution (if the need is strong to have the drop down selection of All People), is to create a dummy item in the hierarchy which can be selected and treated as a "normal" child item Hope that helps David ... View more

Hi - I'm glad you solved it, but it is not recommended to change the settings below the line. To use the certificate, you should to put the following after the operation statement   Operation=-certificate "certificate location.cer" - file ..... -put etc..   Happy Anaplanning       ... View more

Hi The solution here is to create a module that has the parent and other proprties as line items. The formula for the parent is PARENT(ITEM(listname)) You can then publish the module and hide/show just the required line items It is also best practice to create "information modules" to hold the list properties; these then show up in the model map and you can also utilise the formula editor. I hope that helps David ... View more