Understanding Dynamics 365 Business Process Flow Data Model following changes in December 2016 release (v 8.2)

Microsoft Dynamics 365 December 2016 release (version 8.2) included some significant changes to Dynamics CRM Business Process Flow data model and entities structure.

In the new Model, every time a business process flow is activated, a custom entity is automatically created to store the activated business process flow instances.

Before that, every time you create a business process flow, it is stored in the Workflow entity (https://msdn.microsoft.com/en-gb/library/mt622427.aspx).

The Workflow entity stores the business process flow definition. So once the entity is created, it is always in Draft state and its definition is stored in Workflow entity. XAML property is where the definition is stored and is mandatory/required.

Once you activate a business process flow definition (by changing the state of the corresponding Workflow entity record), a custom entity with the following name is automatically created to store the activated business process flow instances:

<activesolutionprefix>_<uniquename>

More details can be found in this MSDN Article here:

https://msdn.microsoft.com/en-gb/library/dn481586.aspx

There is also the Process Stages Entity which contains: Step metadata for process stage (Client Data). It also contains stage Category (Qualify, Develop, Propose, etc.) as well as the Stage Name.

Properties represent fields of data stored in the entity. Some properties are read-only.

Name Type Details
clientdata Edm.String Description: Step metadata for process stage

Display Name: Client Data

Read-only property

owningbusinessunit Edm.Guid Description: Select the business unit that owns the record.

Display Name: Owning Business Unit

Read-only property

primaryentitytypecode Edm.String Description: Primary entity associated with the stage.

Display Name: Primary Entity

processstageid Edm.Guid Description: Shows the ID of the process stage record.

Display Name: Process Stage

stagecategory Edm.Int32 Description: Select the category of the sales process.

Default Options:

0 : Qualify
1 : Develop
2 : Propose
3 : Close
4 : Identify
5 : Research
6 : Resolve
7 : Approval

Display Name: Stage Category

stagename Edm.String Description: Type a name for the process stage.

Display Name: Process Stage Name

versionnumber Edm.Int64 Description: Version number of the process stage.

Display Name: Version Number

Read-only property

More information on the ProcessStages entity is here:

https://msdn.microsoft.com/en-us/library/mt790421.aspx

Finally, here is a Dynamics Community post with few more information and discussion on this subject:

https://community.dynamics.com/crm/f/117/t/241128

Introducing Microsoft Dynamics 365 Business Edition and its core functionality from the Dynamics Roadmap site

As most of you know, Microsoft has been working hard on releasing the highly anticipated Dynamics 365 Business Edition which targets small and medium businesses who do not require the full functionality of Dynamics 365 Platform.

Personally, I have been really looking forward to this version as quite a few of smaller size clients are eager to opt for this more focused version instead of the full platform. The Dynamics Business Edition will allow Microsoft Partners to target the SMB market more effectively by providing a solution that fits their size and their requirements.

The publicly available Dynamics Roadmap website (http://roadmap.dynamics.com) lists a number of functionalities in the new Dynamics 365 Business Edition. some of the functionalities currently being developed in the Sales Module of the business edition are:

  • Lead to Cash
  • Microsoft Dynamics 365 Connector for LinkedIn Lead Gen Forms
  • Quick Start Wizard
  • Simplified setup of Exchange and SharePoint integration

Over the next few days, I’ll be covering some of these new functionalities in Dynamics 365 Business edition in separate blog posts.

In the meantime, you can get the full details about the Sales module of the Dynamics 365 Business Edition can be found here:

https://roadmap.dynamics.com/#edition=1#application=326f31ea-2992-e611-80dc-c4346bac0910#area=#status=c3ba828c-ae97-e611-80df-c4346baceb68

Hope this helps!