Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2020 release wave 1 Discover 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 Timeline
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
When opening a custom entity in the UCI, the timeline displays an error:
When checking this in the old interface it appears correct
Anyone else seeing this?
Clear the cache and try, also try to open the same in another browser.
I faced the same kind of issues.
Have tried both Firefox and Chrome, with both caches cleared.
It actually pauses on a breakpoint in App.js when loading.
First, please refer to this support: https://support.microsoft.com/en-sg/help/4480001/timeline-does-not-render-and-shows-records-could-not-be-loaded
You can contact the customer support and provide the details about this error and ask them to increase the QueryLinkEntityLimit setting for your organization.
Note: This setting will affect all calls in the organization that have link-entities and might decrease performance for calls that have very high link-entity count. However, the performance hit should not be significant if we are increasing the limit by a single digit.
If the customer has created custom activities and is using card forms for them, they can disable the card forms in order to reduce the number of link-entities in the batch request. This can be achieved by doing the following steps:
It is also possible to not include a custom activity at all in the timeline if it is not useful:
Then please refer to this theme: https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/279479/case-timeline-showing-unexpected-error
Going to Settings | Customizations | Security Roles | Customer Service Representative
Changing the Read permission in the Customization tab for Solution (see below).
Hi Lu Hao,
Thank you for the detailed response.
Regarding Mitigation 1:
I make two batch requests to '/v9.0/activitypointers/Microsoft.Dynamics.CRM.RetrieveTimelineWallRecords'. 1 succeeds and 1 fails. The failure is "object reference not set to an instance of an object" - not the "link entity" error reported in your support page.
Followed the steps and it didn't improve. The timeline only shows Email, Task and Phone Call - no custom entities or cards.
Regarding the last suggestions, the issue persists on my System Admin account, so i don't believe it is an issue with the security roles.
Thank you for your help, i will still get in touch with support as you suggested.
I just received a message from Microsoft that it is actually a confirmed issue.
Issue Description: Customer are getting Records could not be loaded because an unexpected error occurred in Timeline wall for the custom entities.
Repro Steps: Go to Dynamic’s 365 UCI and select the custom entity and open the record you will see timeline doesn’t render it.
As of now as per Product team discussion we have 3 different ways for mitigation, Any one of the below options will mitigate the customer from the issue.
a) Disabling the FCB.AutoCaptureUseSolutionb) Disabling the Plugin RetrieveTimelineWallRecords ( OOB Plugin ) on RetrieveTimelineWallRecords [ plugin name: Microsoft.Crm.AutoDataCapture.AutoActivityCapturePlugin]c) Turn Off the AutoDataCapture V1 Feature - > Settings SiteMap -> Sales Insights -> "I Agree" Terms and Conditions -> Turn Off the AutoDataCapture.
The actual rollout fix is schedule next week but due to Christmas holidays in USA it has been rescheduled to fix in the January release.
Business Applications communities