Best Practice Deploying Models

[hybrid]

I have a standard app that runs our annual budget process. I normally deploy, import and change the year naming convention (say from 2012 to 2013) and redo all the admin links every year. I'm wondering if I've been doing this the hard way. Seems like I should have a base model that is not referencing the year, when that app complete I should rename it with the specific year "2013" and save it off. I'm just not sure if I can zero out all the data and keep the links correctly pointed on the contributor app if I do it this way. I normally import without the data for the new year so I know everything is zero and referencing properly. I've added several admin links this year and the thought of redoing them is not appealing. :-\ Any advice on the topic would be appreciated.

[ericlfg]

The idea behind your roll over process update is solid:

1. Export the completed application and re-import it under a new name with a year designation added.
2. Zero out the year neutral base model / application to prep it.

Using this strategy your base model never needs to be renamed or copied, which will preserve your admin links, macros, etc that are setup against it.

In this scenario, to zero out the year neutral base model / application before the new period (after you've copied the application), I've found that using the Import Data feature, or a Prepare import macro step to be sufficient.

Import Data feature:
Click on the Import Data text in the CAC and select the Prepare tab; on this screen, you have a listing of your cubes.  Select the check box in the Zero Data and Prepare columns for the cubes you want to clear and then click Prepare in the bottom right.  Run a GTP and this should clear out the cubes you've selected.

Prepare Import macro step:
Create a new new macro and provide a name (Ex: Zero data <base_model_name>) and select the prepare import step (under Development > Import Data).  Select the base model, select the cubes you want to prepare, and select the cubes you want to zero and click OK.  You'll probably want to put in a GTP macro step after the prepare import.

Review and test both of these options to make sure it performs in your environment as you need it to.

Hope it helps!

[mr j]

Sorry if I missed something, why deploy, import, etc..? You want to store the old budget data somewhere in Planning?

How about if you
- had a base model without year in the name
- zero the data in the app as described once the budgeting process is finished
- just entered a new package name for the app with the year designation in "CAC - Application maintenance - GTP options" and for the end user the year would be there. Well, not in the Planning grid, but at least in the package name.

An example I have in mind deals with the years after publish, ie. Data Manager builds add the year where relevant for further processing. For the Contributor app it's irrelevant which year it is, there's just data and everybody knows which year's budget it is  ;)
After finished it's wiped out. Old budget data is stored in database for reporting etc.

[ericlfg]

Hey Mr J,

From what I understand, they want to archive the completed application.  With the method you described, the base model would be zeroed out before any archival processes.  Changing the package name only changes the name assigned to the base model and doesn't provide any duplication processes.  The deployment export / import allows the creation of a completely separate application container that a year specific designation can be assigned to during the import.

[mr j]

Hi eric,

yes, if there's a requirement to archive the entire application then definitely deployment etc. is the process. Just wanted to point out that if it's not necessary to archive the application you could utilize the published data from db and make preparations for budgeting easier (considering Contributor).