Deleting a model in all environments

At my company we use the known topology of environments. Devboxes, pre-test, customer test, UAT, Golden Config and Production. Lately I got the task of uninstalling an under-performing third party ISV module. This was a set of three models checked in from a devbox with source code. My thought were just to remove the models (using modelutil.exe) and check in the changes into TFS. Did not work on every other machine but the one doing the work, this because TFS only makes changes to models and does not delete them. 

The proper way of doing things are to empty out the models, clean them of source code. Build the single deploy-able package (SDP) and install it normally, as if it was a normal code upgrade. The next time you perform this task of code upgrade, we have to download the SDP and add something to it before it gets installed.

First set of tasks

  1. In Visual Studio, in the AOT search for model: "model name", add all elements to new projects by right clicking it.
  2. Delete all elements
  3. Add a single empty class, typically Class1*
  4. In the Model setup of all models using the model you are to remove, un-tick the reference of the model you are removing.
  5. In pending checkins make sure you have your descriptor file as well as your single class and a deletion of all the elements, then check in all the changes
*The reason for this one single class addition is that only model changes get considered by the build machine, if you remove all traces of it will still reside in sandbox environments.

Next time your build machine compiles and builds for code distribution it will insert the SDP without the code of the model(s) you've emptied. Meaning all functionality of your model has been removed but the models themselves remain, the models are to be removed in the next step. 

Second set of tasks

You are to perform a new delivery to your sandbox environments. Perform a build and a new SDP gets uploaded to your Asset Library. 
  1. Download the SDP zip file from your Asset Library (by clicking on the name) on your Devbox or local machine
  2. Create a new text document, for each separate line specify a model name of those your want to export. 
  3. Save the file with the name ModuleToRemove.txt.
  4. Extract the ZIP file from step one
  5. Place the text file in the folder AOSService\Scripts
  6. Zip up the file again so that it keeps it's initial folder structure.
  7. Upload the file to your asset library
  8. Install and the models will be uninstalled fully

Comments

Post a Comment

Popular posts from this blog

Call a simple Logic app from X++

Image
Logic apps can be called manually from D365FO with code I've made a basic Logic App that receive a short JSON. 1. Get JSON schema Get your JSON sample and go here and paste it in  https://www.liquid-technologies.com/online-json-to-schema-converter . Press Generate Schema and you have your schema in the box below. Example JSON : {   "sku": "875828",   "externalMaterialReference": "400267" } Example JSON Schema { "$schema" : "http://json-schema.org/draft-04/schema#" , "type" : "object" , "properties" : { "sku" : { "type" : "string" }, "externalMaterialReference" : { "type" : "string" } }, "required" : [ "sku" , "externalMaterialReference" ] } 2. Create Logic App In the Azure Portal or in your Visual Studio, cre
Read more

SysOperationFramework with use of Query

Image
 The SysOperation framework is very good and effective, but unforutnatly a bit complicated to get in to and do as you want.  I had one case in which a simple table should be updated, the job was to be able to set in batch. Also it had to use a query so that the user could easily set up the ranges as he pleased. Note that I will use the same query for updating the table which I mentioned. So the same query is used all the way through ending in using Quer::updateRecordset For this you need: Data contract class Controller class Service class Simple query oject Action Menu item Main menu where to make the menu item available. 1. Data contract class Note the simple query highlighted in bright yellow .  [DataContractAttribute     , SysOperationGroupAttribute('Parameters',  "Parameters", '1')] internal final class CustAutoCancelUpdateDataContract {     str             packedQuery;     MCRAutoCancel   autoCancel;     public Query getQuery()     {         return new Qu
Read more

Retail Attributes on sales lines

Image
Recently I've dived into Retail. There will be some posts about retail and the problems I've faced with solutions. First off will be the Retail Attributes, they can be problematic here is a data base diagram illustrating a simplyfied view, assuming the value is of type text. And here is the select statement for listing all sales lines with their attributes.         SalesTable salesTable;         SalesLine salesLine;         RetailSalesTableInstanceValue instanceValue;         EcoResAttribute attribute;         EcoResAttributeValue attributeValue;         EcoResTextValue      textValue;     while select salesId                  from  salesLine             join SalesId                   from salesTable                 where salesTable.SalesId == salesLine.SalesId             join SalesId, RecID                 from instanceValue                 where    instanceValue.SalesId == salesLine.SalesId                 &&  
Read more