TRACK OPPORTUNITY SALES STAGE HISTORY

Our Requirement in the business process flow is how we calculate every step time-consuming need to capture and show.


Step 1.
 First, we can create an entity to store the BPF stage history and use real-time workflow to create the new entity records.
Step 2.

 Then create some fields. Add them to the main form.

  • Opportunity – Lookup field
  • Previous- Single line of text field
  • New – Single line of text field
  • From – Date and time field
  • To- Date and time field
  • Duration(hours) – Whole number (Calculated field)
Step 3. Create a calculated field on an entity to calculate the difference between ‘Start Date’ and Now().

Step 4. Create real-time workflow.

Comments

Post a Comment

Hi,

If any one want to give the stagnation and change its most welcome.

Thanks!!
Rajesh Singh.

Popular posts from this blog

Many to Many Relationship in Dynamics CRM 2011.

Image
I get asked about many-to-many (a.k.a. N:N) relationships more than just about any other single topic, so here’s a summary of how they work in Dynamics CRM 2011. I’ll review both “native” and “manual” N:N’s, using a simple Association to Contact relationship to illustrate. This is a classic many-to-many: each association should be able to have multiple contacts associated with it, and each contact should in turn be able to be associated with many associations. Native N:N Relationships With native N:N relationships, you open up an entity for customization, click the N:N relationships link, and click the  New Many to Many Relationship  button and select the entity to create the relationship to. For the Association to Contact N:N relationship, I’ll start from the Association entity: In the previous figure, notice that Do no Display is selected in the Display Option for each side. I only show that to illustrate a point: what this will do is prevent the relationship from be...
Read more

How to use Plugin Profiler to debug Plugins with Plugin Registration Tool in CRM 2011/2013

Image
You are a Dynamics CRM 2011/2013 Developer and you need to develop some plugnis to perform some synchronous/asynchronous operations that need realy a plugin development. You develop your plugins on Visual Studio and you build. You build succesfully your plugins assembly and all seems fine. You use Plugin Registration Tool (PRT) to register your plugin, steps and images. And Now you are doing your test on your records to verify if your plugins works fine or not, and like for me, nothing works from the first time :) So you had a  Busines Process Error  and you want to know why ? It means, you should debug your code. And There is three ways to do it :  -  First way :  If you are using a OnPremise version of Dynamics CRM 2011/2013 and you have your own development server with Visual Studio: * you should copy your code in your server * open it with Visual Studio * put your breakpoints * attach w3p process * And debug When it's ok you can copy yo...
Read more

Append v/s append To.....

Image
Append and Append To are two privileges that most user are not very clear about regarding their functionality. In this article we try to explain the difference between “Append” and “Append To” Privileges and how it affects the user access. Append and Append To basically deal with the entities that are parties to a 1:N relationship or N:1 relationship. Append:  When an entity has the lookup of another entity on its form. It is important that the user have the “Append” privilege on this entity so that it can set the values for the lookups on this entity. For eg: Contact has the lookup of Account on its form so here the user needs to have the “Append” privilege to be able to set the parent account. Append To:  When an entity is available as a lookup on another entity form. It is important that the user have the “Append to” privilege on the entity that is referred to in the lookup so that it can set the values for the lookups of this entity on any other form. For eg: Account ha...
Read more