Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
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 TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Have you encountered this issue before?
Subgrid is working in Classic UI. But not in UCI.
I tried to update the Subgrid View from My Active Contacts View to Active Contacts. Saved and Publish.
But the subgrid view in the Classic UI is not changed and "The view is not available" error is the same in UCI. I already cleared the cache. Opened the application in other browser (Firefox).
But issue is the same.
I published the solution in the default solution. But issue is the same.
On my research I came across the solution on checking the View if Active. The view is active.
Any idea on this?
Thanks in advance.
+ I would recommend to check console by pressing f12 to see if you get the Guid ID .
+ Incase if you get the Guid ID try to run the following web apiquery .
+ yourorgurl/api/data/v9.0/savedqueries(Guid ID if you get it).
Please double check if that Guid is Active.
Incase if you do not get the Guid ID here is what you can do :
Go to the app designer makesure you have the view for the subgrid in the app .
Further if you still not able to resolve it please raise a ticket with MS since we might have to get the access to error traces and act accordingly
Solved the issue by following this reported issue
Business Applications communities