A new behavior of CRM 2015 Vega is to disallow changes to record ownership in a pre-operation plugin. This issue can be a major cliff hanger for systems that implement some form of ownership business logic such as team ownership models. The implications can be far reaching and require major code and security model refactoring. While you can move your ownership business rules to the post operation the implication is that depending on your system design you might have a lot of work to do to update your plugins and users will have to be able to own the records for a short time. This means some systems simply won’t be able to feasibly upgrade until the issue is corrected. The timeline of the fix is unknown. I would say if more customers complain about it the odds are that it will be addressed sooner than later so I would suggest speaking up if this effects you.
**Update March 11, 2015
Moving your ownership assignment to stage 10 appears to be a viable workaround. Ownership assignment will also revert back to its previous capability in the CRM Ara release.
Originally posted on Debajit's Dynamic CRM Blog:
Recently we upgraded from CRM 2013 SP1 to CRM 2015 version for our customer. We have upgraded to CRM 2015 on the first access (FA) version of 2015 that our customer had from Microsoft.
However after upgrading to CRM 2015 and doing a quick sanity check on the environment, we started getting the following error during creating of certain entities.
