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
Have you queried this via Advance find? is it showing null in advance find results?
I have checked on a latest version of CRM and createdon is not null for any plugin trace logs
Yes, I requested it through Andvance to find
CreatedOn is null, but I saw a dependency: we have pluginTraceLog instances with CreatedOn = null from PipelineTraceService
I am seeing this as well. My production instance has over 8 million records like this.
I have checked few instances both online and on-prem, they do not have loads of records but they all have value set for createon.
CreatedOn should not be null and it sounds like caused by a bug in the platform, most probably by a pre-validation or pre-op plugin
I would raise a ticket with MS and get their support to clear the logs.
Since your CRM is on-prem, you can also consider deleting these logs from [dbo].[PluginTraceLogBase]. But since this is not supported, I would recommend you raise this with MS first and they might give you a script to run and clear these. And they may also provide you the details about if the issue is caused by a bug in the platform.
Business Applications communities