Make a copy of our Prod model and make it our DEV Model?

Highlighted
Contributor

Make a copy of our Prod model and make it our DEV Model?

Hi there, 

 

I currently have a DEV model that is not deployed where i create a revision tag, push it to our UAT deployed model, then push it to our Production Deployed model. I want to refresh our DEV model with the latest data in our Prod model. I was wondering if i can take a copy of our Prod model and then make this the DEV model? Will i need to adjust the source model or anything so that when i create a revision tag in this new DEV model, i can push it to UAT and then to Prod? Also, do i need to connect this to our DEV HUB model as well? If anyone can help out that would be much appreciated!

 

Thank you 🙂

Amanda 

9 REPLIES 9
Highlighted
Certified Master Anaplanner

Re: Make a copy of our Prod model and make it our DEV Model?

Hi Amanda,

If you want to make a new DEV model (which is a copy of PROD model) and make that as a DEV model, then ALM sync will break.
To get the PROD data to the DEV model, kindly create a process (Import Actions to load DEV lists/modules) to fetch data from PROD to DEV. This will make sure the DEV model will contain the latest PROD data as and when you run that process.

Let me know if this helps.

Thanks
Sathya
Highlighted
Frequent Contributor

Re: Make a copy of our Prod model and make it our DEV Model?

Hi,

 

Yes you can copy model prod to dev model, but you cant snyc anymore with latest model, New dev to UAT to Prod because New dev have another struktur revision tag (with UAT and Prod).

 

 

Thanks,

 

Panji 

Highlighted
Certified Master Anaplanner

Re: Make a copy of our Prod model and make it our DEV Model?

Hi Amanda-

Yes, you can absolutely do this. You need to be sure to do a couple of things in the correct order, but it is completely possible. 

 

I will refer to your current DEV as "DEV 1", and once we copy PROD then I will refer to it as "DEV 2"

 

-First, we will Copy PROD and Create DEV 2.

-We need to change the Mode of DEV 2 from Deployed to Standard.

-At this time we technically have multiple models that are compatible (DEV 1 and DEV 2), and the next revision tag is the one that is the most important and will make other models incompatible.

-We then want to Archive DEV 1 to not get confused. 

-When our next revision tag is created in DEV 2 then it will be found when running the Compare/Sync in PROD.

 

From there, you will want to go into your Source models and Change the Mapping in DEV 2 to look at your DEV HUB instead of your PROD HUB so that it pulls in data from the corresponding HUB. The source models are considered Production Data, so it will not impact the compatibility for ALM.

 

If you are still uncomfortable doing this, I might recommend doing a quick 10-minute run though by doing the following:

-Create a new model (DEV)

-Create a module or list

-Copy DEV and Make a PROD

-Change the PROD into Deployed Mode

-Make a change in DEV, Revision tag and sync to PROD

-Copy PROD to make DEV2 and change DEV2 to Standard mode

-Create a new module in DEV2, Revision tag, then Sync to PROD

-Test Complete! Now PROD is compatible with DEV2

 

I hope this helps!

Jason

Highlighted
Master Anaplanner/Community Boss

Re: Make a copy of our Prod model and make it our DEV Model?

Hi Amanda and Jason,

As there are multiple answers, just pitching in to add that Jason's is the right approach

Regards,
Anirudh
Highlighted
Certified Master Anaplanner

Re: Make a copy of our Prod model and make it our DEV Model?

Hi Jason,
Quick question:
For example, after a week, if we want to fetch the latest PROD data to DEV2 model, then do we need to do the same steps?

Thanks
Sathya
Highlighted
Certified Master Anaplanner

Re: Make a copy of our Prod model and make it our DEV Model?

Sathya-

Yes, this would just be copying the model and its data from the second that you copy it. Any changes to data thereafter in PROD would not be linked to the DEV2 model. Any future refreshes of the data would then need to run through the same process. If there is a need to constantly keep PROD Data in DEV then there might be a better approach, but in my experience, periodic refreshes of DEV are adequate (I typically do this infrequently like 0-4 times per year depending on the Company and Use Case).

 

Jason

Highlighted
Contributor

Re: Make a copy of our Prod model and make it our DEV Model?

Hi Jason,

Thank you so much for this detailed description! 🙂 I was able to make a copy of both models and now i have the new DEV HUB (copy of Prod HUB) and the new DEV 2 (copy of Prod). I also created a revision tag in both models and pushed it from DEV HUB -> UAT HUB -> Prod HUB and a revision tag in DEV 2 -> UAT 2 -> Prod 2. When i run an action to import data from DEV HUB to DEV 2, i dont see the new data. How do i fix it so that these import actions will work? Thank you! 🙂

Best,
Amanda
Highlighted
Certified Master Anaplanner

Re: Make a copy of our Prod model and make it our DEV Model?

Amanda-

You will need to re-map the model in the Source models:

 

jasonblinn_0-1586982437660.png

 

In this example, I am in my DEV2 model, and I click on Source Models in the Settings. By default the "Mapped To" Section is likely Blank (Or Mapped to PROD because that is what we copied). In this case, I am guessing you want to hook DEV HUB to DEV2 so you can click Edit Mapping and then select the New DEV HUB model. 

 

This will map all Model to model imports from the original model to the new model/correct instance. 

 

Data should flow like this if my understanding is correct:

DEV HUB -> DEV2

TEST HUB -> TEST2

PROD HUB - PROD (this one shouldn't need any changes to the mappings)

 

Let me know if you have further questions!
Jason

 

Highlighted
Master Anaplanner/Community Boss

Re: Make a copy of our Prod model and make it our DEV Model?

Hi Amanda

Whilst the answers are correct and you just basically go along copying, archiving, relinking various models this question needs to be answered...

Why are you wanting to put production data in the dev model? This surely goes against security issues about not having live production data in development areas. Certainly if this were to happen in where I work all sorts of flags would be raised.

The dev model should only contain enough data to be able to prove calculations and data flow working, then onto test where there might be live structures but still "fake" data before going to the prod model where there's live data which often has sensitivity around it.

Andrew