Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
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: 220.127.116.115 and SG Version: 18.104.22.1680 (Scale Group) are not the same. We assumed that the issue will be fixed in Org Version: 22.214.171.1249 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.
Dynamics is completely unusable to our company now since Microsoft update from 8.x to 9 and we are a Microsoft Partner also. Was told early last week that there was a bug and it would be resolved but things are worse. These newer issues started at around 6PM EST and our customer care is at a standstill!
When sending an email from the activities area of any customers case results in an error:An error has occurred. Try this action again. If the problem continues, check the Microsoft Dynamics 365 Community for solutions or contact your organization's Microsoft Dynamics 365 Administrator. Finally, you can contact Microsoft Support. When trying to assign a case it results in an error: Method not found: 'Boolean Microsoft.Crm.Metadata.RuntimeTypeCache.get_IsInitialized()'. When trying to resolve a case it results in an error: Method not found: 'Boolean Microsoft.Crm.Metadata.RuntimeTypeCache.get_IsInitialized()'.
iolo technologies, LLC
Was there any suggestion of how to fix the Field Security issue? We have experienced that very issue today following an upgrade from 8.2 to 9.0.2.
We will raise a ticket, but Im keen to know if we fix this quickly ourselves.
Jeremy: what kind of field security issue do you have?
There is an upcoming update of Dynamics 365 V9.0 that will have many bugs fixed for those who upgrade from 8.x to 9.x, not public yet but it should be out over the next 2-4 weeks or so.
Thanks for the quick reply.
The issue I am facing is the same as that described in 4.A in the original post.
Pre upgrade, a field was set up for field security, but since upgrading, the field is not visible in the Field Security Profile field list, and therefore no users can View/Update/Create this field on any of the records.
I tried to disable field security on the field, but I cant remove it without having access to the field via field security!
The field is used for a number of filtered views/dashboards etc, so the impact is quite far reaching.
Any indication of how this specific issue was address would be appreciated!
Has anyone seen an issue where the processid field does not get populated when changing stages on an Opportunity with a business process flow defined? We are getting blank processid's after we upgraded our org from 8.2 to 9.0 and I cannot find anything about this issue.
how to stop the grade from 8.2 to 9?
Easy… sit this update out. You can skip up to 2 updates… that means you can also skip the one the one that's due this fall if you choose to.
I am not able to figure out how to skip. I am in 8.2 now and the target release is 9.0
Richxyz1, this might be helpful How to determine which Business Process Flow (BPF) instance is shown when a record is opened
Dear Community Members
According to Microsoft the “Field Security issue”, which seems to be fixed already on the current 9.0 version.
I upgraded from 8.2 to v126.96.36.1990 on Monday September 3rd and I have a field that has lost its field security profile.
The field is opportunity.estimatedvalue - did anyone find a resolution for this issue?
Few weeks before when I checked with Microsoft support team, they mention as below.
We are aware of the field security issue you referenced below and a fix is put in place. To reinforce what I mentioned in the thread below:
We review and prioritize all reported issues and deliver fixes on weekly basis. If an issue is known, we prioritize and fix it.
Whether the issue happened on development/UAT environment or Production env?
Just on curiosity:
I would like to know, what are the other issues you faced after the upgrade.
Since we are planning for our customer in few weeks.
We've recently encountered a similar issue with custom entity subgrid,
Did you by any chance receive a feedback from MS support regarding this issue?
Hi Andrew - eventually, yes I did. For us at least the issue was caused by the mappings in the 1:n relationship for the grid. The upgrade had corrupted them. There is a "generate mappings" button under the "more actions" link. Regenerating the mappings fixed the issue.
Customisations --> Customise the System --> Your Entity --> The 1:n relationship in question --> Mappings --> More Actions --> Generate Mappings.
Much appreciated, you really helped!
Strangely enough, the error wasn't caused by the rollup, but appeared when transfering solution to a diffent server.
Business Applications communities