Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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
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