title: Code Upgrade Conflicts on objects that only exist in VAR layer
body: <p>Having just completed the painful process of upgrading all our custom code from AX 2012 RTM to AX 2012 R2, we are now in the process of applying CU7.</p>
  
  <p>When running the 'Detect Code Upgrade Conflicts' process, it has reported a large number of 'Deletion Conflicts' on our custom AOT objects (mainly tables, classes, and strangely configuration keys). </p>
  
  <p>These custom objects only exist in the VAR layer, and therefore we would assume have no conflicts with sys / syp layers. Some of the methods it reports as conflicting, are simply a class declaration !</p>
  
  <p>I should add - I understand that I can simply mark them as resolved, but I'd like to get to the bottom of why the system thinks there are conflicts on these objects, in case we have some kind of underlying problem with the models and/or we might hit this again with next CU / Hotfix installation.</p>
  
  <p>Does anyone have any ideas ?</p>
  
  <p>Thanks in advance !</p>