Check out the latest Customer Service updates!Learn about the key capabilities and features of Dynamics 365 Customer Service and experience some of the new features.
Download overview guide | Watch Customer Service 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
I use a service account to full copy a PROD instance to a sandbox instance. When a user(admin role) created an account record in sandbox, a ghost record will be created with the same GUID and different account number by a system service account in PROD. Is anybody know why the ghost record get created? How to stop this? Many thanks.
This is weird. Is there any plugin or JS that has the environment hard coded in it and where it creates records?
I don't see any.
How is the account record being created? Is it being input into CRM, or into a Portal?
It's been created into PROD instance, by a system admin account with a license assigned.
Is it being created by a workflow, or by a plugin?
No idea. No system job in PROD instance related to this creation.
This would be the first thing I would answer... iss it a workflow or a Plugin that is writing the record.
You should be able to figure this out fairly quickly. You can look in the default solution under "process" for a workflow that is firing; however, if there are a lot of workflows, this could be tedious. A better way would be to connect to your Dynamics instance with the Plugin Registration tool to see if a plug is registered... if you have the admin access to do so. Do you have admin access? Do you also have access to the Plugin Registration tool?
Who would have done a plugin (or a workflow)? Is that person no longer available? Sorry to ask so many questions - but this is no simple issue, and there are many ways to copy a record.
And of course, you should check under you SANDBOX instance, as that would be where the workflow or plugin would be running that would copy a record to PROD upon creation in the Sandbox. On the surface, it sounds to me like the plugin is firing, and copying the record to an instance with a GUID that is now in PROD. No clue how that would have happened, but it makes more sense if it's a plugin that's firing than if it was a workflow.
Your questions are great.
I can see the audit log showing the record is created by a system admin service account.
By which process? No idea.
How? Whenever an account record is created in Copied instance, a ghost record will be created into the PROD instance.
Look into process list or Plugin Registration tool doesn't really help, as the create action doesn't look like triggered by an event happened within the PROD instance.
I'm sorry; I edited my response and added that you should check under the SANDBOX instance, but most likely you missed that as I edited it a bit late.
This is occurring whenever an admin creates an account record in the SANDBOX instance, correct? Something then copies the record into a "ghost" record in the PROD instance, right?
If so, this means that the workflow or plugin is on the SANDBOX instance, and is triggered on create of the record. That's where I would start looking.
BTW... are these instances On Premise, or in the cloud?
Two "yes" to your questions. I disable all the plugin steps and workflow registered on the account entity, and then enabled them one by one. And we found one of the workflows updating the account triggered by create and update event of the account entity, is causing the issue, once it's turned on.
It's on cloud.
Great! Does this mean your issue is resolved, or are you still experiencing it?
Yes and No. We still need the workflow, and we cannot figure out why a workflow like this in the sandbox creates a ghost record in PROD.
Can you share a screenshot of the workflow? Maybe I can take a look at it.
Business Applications communities