CRM fields

     Dynamics crm 2016 gave us a revolutionary option to work with solutions more granularly, option for true inheritance from managed solutions, build-in holding solution option etc.       In the same time some old “diseases” are still there. Managing dev and QA instances, I’ve found an issue that appears as a generic error in log file and cannot be tracked with tracer or event viewer. By my experience, the issue may happen if: 1.        You deleted a relationship and then created a field with same name in the same entity. 2.        You deleted a local option set field and created a  field based on global option set in the same entity with the same name.         The symptom of those two issues will appear in the target crm instance in the import log file: “ The content of the import file is not valid. You must select a text file ”. The fix is to make manual changes to target. In case you cannot make manual changes due to managed nature of target solution you might