Fixing Managed Components when they ahve become Unmanaged RRS feed

  • Question

  • I work with a Managed Solution which is rolled out on a regular basis to a dozen systems.

    One issue I have is that from time to time the JS files do not get replaced locally.  Probably this is due to an Unmanaged change happening on the target server.  We have many target servers so it is hard to spot this issue.

    I don't want to force an overwrite of the Managed solution because some of these systems have other managed solutions which may have been installed after ours so our solution might bubble to the top and adversely effect forms etc.

    Any ideas on how to manage this sort of thing?

    I had thought that I might be able to produce a temporary solution with just the JS files and force an overwrite on that, then install my solution normally and then remove the temporary solution.

    I have also contemplated writing a script to check the versions installed across all CRMs to highlight unmanaged customizations on these types of objects.  Maybe I can fix them in the script too.

    I did try to delete the Unmanaged JS file before installing the solution, however the unmanaged version came back.  I wondered if this was because it takes time to be fully deleted and I hadn't left enough time between delete and solution install.  Can anyone confirm this behaviour?

    Sorry this is a ramble but there are items such as Web Resources and Reports which may become Unmanaged but we would always want to be overwritten by a Solution install and others such as Forms and Views which should be unique to the particular system and we don't want to mess with those.

    Friday, August 9, 2013 10:55 AM

All replies

  • In the end I forced the managed solution over the top and this solved the problem.

    • Proposed as answer by gordonjohnston Thursday, October 3, 2013 9:33 AM
    Thursday, October 3, 2013 9:33 AM