When creating records using the Dataverse Web API, the default behavior is to
return a successful response without including the record data in the response
body. A standard create request does provide access to the newly created
record’s GUID thr...
Microsoft recently introduced a preview feature for Dataverse Bulk Delete Jobs
that provides additional control over bulk delete processing. One of the new
options available when creating a bulk delete job through the API is
RunJobForSandbox. Acco...
Please refer to the post below, which provides a clear explanation of how
RetrieveDependenciesForDeleteRequest works and how it can be used to identify
dependencies.
Recently, while cleaning up some old customizations in Dynamics 365, we came
across an interesting dependency issue that was not immediately obvious from the
user interface. What initially looked like a simple Business Process Flow
deletion turned...
When running marketing campaigns, UTM parameters help us understand where our
leads are coming from. They help us track whether a lead came from Google Ads,
Facebook campaigns, email campaigns, or some other source. Recently while
working with a D...
While working on a Lead Disqualification scenario in Dynamics 365, we ran into a
strange issue. When trying to Disqualify a Lead, Dynamics 365 was showing the
generic error message: “Please ensure all required fields are filled out and
have valid ...
We were working on a data migration requirement where we needed to preserve
system fields like created on and modified on. For Created On, things are
straightforward. We can use the overriddencreatedon field, something we had
already explored earl...
We recently worked on a requirement where we customized an out-of-the-box ribbon
button in Dynamics 365 — specifically, the Reactivate Lead button. We had
renamed it to ‘Reactivate’ as part of an earlier customization. Below is how the
button appe...