Good day
I would like to ask how do we archive a prod model without disrupting compatibility for ALM. When i try to archive the prod model, it automatically creates a revision tag thus disrupting compatibility.
Thank you!
Hi @rlgarcia06 ,
You can archive the deployed model from the model settings and changing the mode. You need to do this directly in the Deployed model only.
Change the mode of the model from Deployed to Archived.
Now when you want to bring that model back, just make sure you change the mode from Archived to Deployed.
By following the above steps your ALM compatibility will remain intact. Do not worry
I hope this helps
~Anand
@rlgarcia06
Your ALM will remain intact until you change your deployed model to standard mode.So do directly deployed from archive and archive to deployed to keep ALM working.
I would like to understand more why would you like to archive a production model and bring it back again for ALM?
Thanks
Abhay
Sorry I mean I need to copy and archive a Prod model without disrupting compatibilty for ALM. This is to back up the production model. Thank you!
You can 'Copy and Archive' as well. It wont break your ALM compatibility. Just make sure while unarchiving the model, change the mode to deployed and not standard.
Hi @rlgarcia06
You can copy and archive the prod model in deployed mode directly from manage models and going to the copy and archive. This won't break the compatibility of the model.
Regards
Subhashree
Hi, i have a source that uses a connection to Skutrak, and i selected 3 columns when i created the source, now i want to bring in a 4th column, do i have to recreate a source from scratch and then use that in a new transformation view and do all the work i did again, or can i update the source column selection, and add the…
We have 2 dataspaces (Training and Current), the training one had a link to a list in a Model. When i tried to add a link to the same list in the Current dataspace, the link showed as ticked and i could not select it. Does this mean you cannot link to the same source in 2 different dataspaces? It shows a tick in the LINK…
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…