Background - We are running on MS Dynamics CRM Online (8.1.0.526). Users are using this system in PROD and other than that we have two environments - DEV and TEST. We have got 8 custom Activity entities in the system.
There is a custom developed base solution alredy deployed into TEST and PROD. When we went live, We created an UNMANAGED solution (1.0.0.0) in DEV and then deployed the corresponding MANAGED solution (1.0.0.0) into TEST and PROD (Which is working as expected).
Now, as we are working upon the next release, we created another UNMANAGED solution (1.1.0.0) in DEV and added some of the existing entities and workflows which were altered. As we have added existing components into this newly created UNMANAGED solution (1.1.0.0) in DEV, obviously, these components do exist in the base solution (1.0.0.0) too. We were able to successfully import the corresponding MANAGED solution (1.1.0.0) into TEST environment and the import log looked clean (no errors, no issues and no unprocessed records too). There were few warnings related to the workflows which said - The said workflow has been deactivated and replaced. So, no issues what so ever.
Now, here comes the ISSUE :- Few of the custom developed views on the Activity entity have the filter criteria on 'Activity Type' and have the custom Activity entities selected in them. All 8 custom Activity entities are selected under the 'Selected Values' in the DEV environment. For some strange reason, after the Managed solution (1.1.0.0) was imported into TEST, 2 of the custom Activity entities got removed from the 'Selected Values' to the 'Available Values' under the 'Edit Filter Criteria' in respective 'Views'. As mentioned earlier, this issue was not highlighted in the Import Log File. However, when you try to click upon the 'Edit Filter Criteria' on any of the affected views, it gives a WARNING and says - This condition has one or more list values that no longer exist in the system.
Interestingly, the missing list values do exist in the system and are available for the selection under the 'Available Values' in 'Edit Filter Criteria'. I did check the customisations.xml and it seems that the underlying FetchXML has all the 8 values mentioned in there.
I assume, I can select these values manually and save them. However, I did not want to do that until I am sure of the root cause and any other fix around this. I assume, doing it manually in TEST where these changes lie under MANAGED solution (1.1.0.0) is not advisable.
Could anyone suggest what would have caused this and what would be an appropriate fix?