You’re offline. This is a read only version of the page.
Announcements
It seems like an upgrade from 8.2 to 9.0 of Dynamics 365 will cause the following:
1. [SOLVED] The field service solution upgrade will fail causing major failures in many core functionalities.
Solution: MS Support runs mitigation scripts on your instance DB to resolve this issue.
2. [SOLVED] Some of the ribbon buttons might stop working (Important ones like Qualify, Add Product) - this is different for different instances.
Solution: This appeared to be a version 9.0 bug with earlier releases and the current releases seem to report no issues. We hope this continues to be the case moving forward. A move from 8.2 to 9.0 should no longer cause this failure.
3. Some entities will not create at all (unexpected errors) (I have seen the Quotes entity so far throwing this).
Solution: Still not sure if this is something that will happen or not when you upgrade, some instances report this and some don't.
4. Some other issues reported by clients:
A. Field security broken on one field which was no longer listed under Field Security Profiles (& could not disable it either as it said I don't have sufficient premissions-> Sys Admin role)
B. [SOLVED] Unable to open Documents from entities. Solution: Again this was a bug in earlier releases and has been mitigated. Reply if you are still facing this, I've seen it solved for a few instances.
C. ClientUtility not found script error in SalesHub
D. Customisation of any App generates error and can't edit it
Reported by members
5. At least one of our custom entities can't be created via a subgrid. Creating the child entity first and then setting the parent lookup works OK, but when using the new button on a subgrid or associated view results in an error "Invalid Argument: System.ArgumentNullException: Value cannot be null." This is thrown by an internal CRM method: Microsoft.Crm.Metadata.ServerDynamicMetadataCache.TryGetEntity(String entityName, NameMappingType mapping) The parameter entityName is the one that is null. Before anyone asks, there are no custom plugins or workflows in play. This worked fine in V8.2 and was broken as soon as the v9 upgrade was completed.
Update: no response from Support in 9 days!!! That's right 9 days after upgrading our production instance, and raising a ticket to support, I've still had no response. I can see the ticket in O365 Admin, but no response.
6. Organization Insights - interactive dashboard is broken in V9. For us the whole dashboard failed to load (spinning icon). After uninstalling and re-installing the Org Insights solution the dashboard loads, but the calendar controls are broken, so you can't filter anything by date range.
Update: response after 5 days.... Support are aware of the issue and they say the Product Team are aware. They also recommended I enter a suggestion in the ideas pages?! Errr.... I suggest the Product Team fixes it :). Support ticket closed. Back of the net! "Thank you for choosing Microsoft, we hope you have a good day". Grrrr.
A fresh install of V9.0 on the other hand can result in:
1. [SOLVED] Unable to add workflow to the Order Line entity - so avoiding the use of the order line entity in your customisations is smart.
Solution (requires raising a ticket with Microsoft): Microsoft says that this has been fixed by an update, the fresh install of the Organisation version: 9.0.1.425 and SG Version: 9.0.1.510 (Scale Group) are not the same. We assumed that the issue will be fixed in Org Version: 9.0.1.459 so I raised a ticket with Microsoft to upgrade the Organisation version to match with the SG version. This should fix the problem above.
Please contribute to this list or correct it if you have information on the latest upgrade issues. Some of the members here reported some of the issues above as well, so I will keep an eye on what they say. Do ask general questions here about upgrades.
*This post is locked for comments
When filtering some views by an OptionSet in the view will display "unhandled" rather than the OptionSet values. Closing the filter and re-opening (twice? 3 times?) will cause the filter to show the appropriate OptionSet values again.
If you click on "view records" on a Chart that is displayed on a Form that shows child records will display ALL records of the same type rather than the subset of child records you see on the Form.
Filtering Views no longer updates the associated Chart. Drilling down on the Chart will update the values selected in the View as before.
Filtering Views no longer updates the associated Chart. Drilling down on the Chart will update the values selected in the View as before.
If you click on "view records" on a Chart that is displayed on a Form that shows child records will display ALL records of the same type rather than the subset of child records you see on the Form.
When filtering some views by an OptionSet in the view will display "unhandled" rather than the OptionSet values. Closing the filter and re-opening (twice? 3 times?) will cause the filter to show the appropriate OptionSet values again.
Another update - not out of the woods yet - as Lubnah reported earlier, another potential effect of the field security issue is the failure, with a red cross, no hover text, of the Existing Product logic when adding products to Quotes or Orders.
For us this has occurred only for new products created since the upgrade and then added via the subgrid. If you try the same addition via the associated view it will fail too, but you get an error log that seems to implicate field service plug-ins. Not sure yet which secured field, if any, is the cause of this, waiting for another Microsoft response.....
Hi All,
An update Microsoft eventually responded to the support request, and reinstated the field secured fields that had disappeared from the field security profiles over the weekend. The after-effect was that the actual settings in the profiles for those reinstated fields had all been reset to no permissions and we then found that the sandbox fields were also all at no permissions, even though we had never lost the actual fields from the sandbox profiles - so we then had no record of what the settings should be, and had to reinvent them.
Conclusion: when sandbox was upgraded to release 9 the same fields had been affected but in a lesser way and since there was no production activity occurring there, the effects were not noticed.
Mike
Hi All,
Field security problem still occurring with upgrade to version 1710 (9.1.0.294) - hope Microsoft can fix it quickly because it is integral to client's production operations. It did not occur when Sandbox was upgraded to the same version, in fact there were no problems at all - so you just can't relax!
Mike
Make sure under CRM system settings you have "Use legacy form rendering" turned on. Helped me.
HI Raja,
Apologies for the delay in replying. The issue occured in a Sandbox dev environment. To resolve, I rolled back the update (copied UAT to dev) and removed field security. On review, we discovered it was not really necessary.
Our production update is scheduled for three weeks.
Thanks
Hi Laco,
I would like to know how did u fix the Field Security broken issue.
Thanks.
#1
André Arnaud de Cal...
293,411
Super User 2025 Season 1
#2
Martin Dráb
232,552
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (