Share
Report
70Having resolved my confusion with model management & mapping of LCS upgrade projects, I believe the code has been appropriately refactored to extensions in a single Visual Studio project & model, so I'm trying to remove the overlaying created by the code upgrade tool. Currently, Visual Studio is giving me 7 errors that feel like they're related to these unwanted models:
- The model 'Application Suite.USR Model' belongs to the package 'ApplicationSuite' that is blocked from customization. You cannot have more than one model in this package.
- The model 'Application Suite.VAR Model' belongs to the package 'ApplicationSuite' that is blocked from customization. You cannot have more than one model in this package.
- The model 'Application Suite.WarningRemoval' belongs to the package 'ApplicationSuite' that is blocked from customization. You cannot have more than one model in this package.
- The model 'Electronic Reporting Application Suite Integration' belongs to the package 'ApplicationSuite' that is blocked from customization. You cannot have more than one model in this package.
- The model 'Foundation' belongs to the package 'ApplicationSuite' that is blocked from customization. You cannot have more than one model in this package.
- The model 'SCMControls' belongs to the package 'ApplicationSuite' that is blocked from customization. You cannot have more than one model in this package.
- The model 'Tax Engine Application Suite Integration' belongs to the package 'ApplicationSuite' that is blocked from customization. You cannot have more than one model in this package.
Whilst the last four of these seven are, I believe, standard models within the ApplicationSuite package, I'm happy that the first three need removing. I've seen discussions reinforcing my belief that I need to delete the "sub models" created by the LCS code upgrade on another forum thread, and I've been doing this by deleting the overlayed object definitions within Visual Studio & using the Dynamics 365 > Build models menu item to build the relevant models. Even after that, I'm still seeing some subfolders that I'm pretty confident shouldn't be necessary in AosService/PackagesLocalDirectory/ApplicationSuite: I've got (1) ApplicationSuite.USR Model, (2) ApplicationSuite.VAR Model and (3) ApplicationSuite.WarningRemoval as models that I know existed in 2012 but I would have said I'd "removed" by deleting all child objects in either the UpgradeSolution or CodeMergeSolution VS projects that were created by the LCS code upgrade. I did try stopping the batch, DIXF & W3WP service & deleting these three folders before building the ApplicationSuite model in Visual Studio, but the folders return at this point. Can anyone please advise what else I should be refreshing to get rid of these models?
All responses (
Answers (
