Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
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
We currently have Dynamics 365 Production and Sandbox instances. I have noticed weird behavior after refreshing the sandbox, by following the steps to copy everything in the production instance over the sandbox. When we create a lead in the Sandbox, a blank record gets created in production. When we move that lead through the process and qualify it, an opportunity record gets created in the sandbox, but we also get a blank opportunity record in production.
I was under the impression that these instances were separate from each other and they should not talk back and forth. Searches online come up with nothing helpful. Has anyone seen this type of issue before?
I should state that i have only been working in Dynamics 365 for a couple months now. Before I began helping, there was only a prod instance. The sandbox was created after I asked for a place to develop changes and then I was given full admin access to do what i needed to in both environments.
That is strange behavior. Does this happen with any other entities or just with creating a lead? Do they have any scripts running that might be referencing the Prod URL? You are correct that these should be separate instances. You might need to create support ticket with Microsoft.
Thank you for the reply. It only seems to affect the Lead entity on initial creation. But when the lead is qualified and turns into an opportunity, an empty opportunity record shows up in prod.
Where might I go to look for scripts? Would it be tied to a Business Process?
Can you check if you have any flow/power automate or logic app which is getting triggered from sandbox instance and action in flow pointing to prod which is creating record in Prod.
I've checked all the custom Flows that I see and none of them trigger from the sandbox and act on production. I have some flows created in the sandbox environment, I turned them off and the behavior still exists.
Business Applications communities