Personalized Community is here!
Quickly customize your community to find the content you seek.
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 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 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
This issue is has been reported elsewhere on the old ADX Studio forums. See: https://community.adxstudio.com/forums/adxstudio-portals/7ecfe132-f369-e611-9403-000d3a10c795#post-7fcfe132-f369-e611-9403-000d3a10c795
Just to elaborate:
This bug requires a few obscure ingredients to present itself, it’s kind of like the perfect storm.
Steps that cause the issue to occur:
If the above conditions are satisfied then any further action on the subgrid edit form will result in a “record not found” message.
Has anyone else experienced this or found a workaround?
We are using Dynamics CRM 2013
Just putting a note here for anyone stung by this issue:
This has been confirmed by Microsoft premier support as a bug in ADX. This will be patched in an upcoming release.
Business Applications communities