{Quick Fix} Qualify button on Lead not working in Dynamics 365

Debajit's Dynamic CRM Blog

I have been working with Customer IT Team on a Dynamics 365 project and we have been doing kind of fancy stuffs, new features and what not. And suddenly we are being reported that Qualify button on lead form is not working. However the same is working from the “Home Page grid”.

First glance and I thought – Must be some silly tampering with the Qualify button. However one quick inspection with Ribbon Workbench negated that suspicion. How can such a stuff working for years can’t work all of a sudden in our environment? Product Bug? Can’t be for sure. It’s been working for years!

After beating around the bush, we finally decided to keep a back-up of our customizations and restored vanilla lead form from different environment. Qualify button started working like piece of cake.

In curiosity, to find out what caused the issue, I started removing one field…

View original post 76 more words

TFS vs. Git…or is it TFS with Git?

Good read on – Git and TFVC

Johan Leino

Maybe you ended up on this post because you searched for ‘Git vs. TFS’. I hope so.
I have seen some debate going on for some time now in twitter about Git versus TFS (here are some examples):


If that’s the case I think you’re looking at it from the wrong angle, so to say. It really a matter of centralized vs. distributed version control.
Here’s how Microsoft actually explains it when you choose version control while creating a new project in Team Foundation Service:


Team Foundation Version Control (TFVC) uses a single, centralized server repository to track and version files. Local changes are always checked in to the central server where other developers can get the latest changes.

Git is a Distributed Version Control System (DVCS) that uses a local repository to track and version files. Changes are shared with other developers by pushing and pulling changes through…

View original post 1,731 more words

Empty or Disable cache while working with Web resources in Dynamics 365 (Chrome)

Most of the time while developing Web Resource we need to frequently update and publish it. We need to make sure that it is not cached and our changes are reflected instantly on publish.

For Chrome,

Open the Developer Tools (F12)

Press and hold the reload button and select “Empty Cache and Hard Reload” to have changes reflected.


The other option à Developer tools – Settings – Preferences

Hope it helps..

Update Schedule of existing Azure WebJobs (triggered)

Suppose we have following WebJob deployed in Azure of type Triggered.

And now we want to update its schedule.

To do so,

Open the App Service Editor

Update the CRON expression in settings.job (in case of scheduled web job), if the file is not there we can create and add it.

This makes the Webjob to run every 1 minute.

Back in our Webjob we can see the schedule updated.

Inside the logs à

More details –


Hope it helps..


Using log4net with Azure WebJobs

To get started, let us create a C# Console Application and add the NuGet Package for log4net.

Update the App.Config with log4net configuration.

The most important part here is value of file.

The D:\Home\LogFiles is the path where our WebJob can write to.


Inside our program.cs initialize the log4net.

Publish the WebJob to Azure.

Open the Kudo, we can see the Folder created

And our log file

Get all the details here


Hope it helps..