Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I get the following error when adding a date field to a chart in CRM 2011 on-premise.
"An error occurred while the chart was rendering"
The database has "is_trustworthy" set to true and CLR is enabled. I only get this error if the date field is added to the horizontal axis and not the other way round. The user I am signed in as it a full admin and the setup user for CRM.
This may be related to another issue I posted https://community.dynamics.com/crm/f/117/t/137448.aspx
To add to this, I have created test organisation on the same server and I get the same issue. It looks like the issue is server side rather than organisation specific.
Can you check if it is on the information form or the main form. Are you able to add other fields, Are you able to add the same field on other forms. Is their script running on the same form. Do you have privileges for customization at org level.
Microsoft Dynamics CRM
I face same problem since last week.
Non of the date fields could be used to create any chart. I tried different entities & different forms, non is working. Always the same error "an error occured while chart was rendering".
I have no idea how to solve that...
(I´ve complete priveleges)
I just ran the standard (OOTB) charts tonight for the first time on a CRM 2011 on-premise instance, roll-up 15 and encountered the same issues.
What roll-up are you on? What browsers have you tried?
Have you tried this?
I was also facing same issue but after enable CLR and restart all the SQL Services, everything is working fine.
Business Applications communities