How Microsoft Dynamics CRM workflow definitions are stored in the SQL Database - Blogs
X
17Jun

How Microsoft Dynamics CRM workflow definitions are stored in the SQL Database

Microsoft Dynamics CRM, is one of the prominent offerings from the Microsoft Dynamics family of ERP and CRM products. It is quite a long time now that MS CRM is in the marketplace. We came across a very odd request from one of our clients, asking us develop a tool which will generate documentation for the CRM workflows. The definition of the workflows in MS CRM is quite intuitive and easy to use. However, the way this data is stored in the CRM SQL database is not that straight forward. Our team did some Googling without much success. All the blogs available seemed to be talking more about how to define workflows, what are the best practices to be followed while defining workflows, how effectively workflows can be used, etc. etc. But none of them really explained about how the metadata for the workflows are stored in the database. Also, MSDN was not of much help. So, we decided to look deeper into this subject ourselves.

We identified the table WorkflowBase, which seemed to be the most probable one to hold these metadata settings. We explored the table and found that our hunch was correct. We found most of the settings stored in this table, but were not able to find the step details. Then we found that these data components are stored in a field called XAML, in a XAML format. The data is not stored in a very straight forward manner, though it was good to know that the values stored were not encrypted. It is just that the data was formatted into some pre-defined XML format. You can see one of the sample XAML data below:

XAML

Decoding the XAML was another challenge faced by the team, because the way the data elements are stored is not something conventional, something which we don’t come across frequently. The team looked into the data to pinpoint the elements (text, numbers, etc.) to identify how the metadata is stored.  Finally, we were able to decipher the XAML formatted text stored and we made a sample output like the following: 

WFOutput

The journey through the storage layers of Dynamics CRM was quite interesting, and we were able to reach to what we had set-off for.

If you wish to discuss further on this topic, please feel free to drop me an email to chinmoy.roy@ecanarys.com

Related

Manage My SMS

.main{width:677px;float:left;font: 13px/1.5 'tahoma', verdana, arial, sans-serif;}#slider1 { height:...

Read More >

Autofill RecVariable Name in DynamicsNAV 2015

I discovered something quite interesting couple of week back and I thought it was worth sharing.When...

Read More >

Software Services

The whole world has come to realize the role played by Information Technology and looking at ways to...

Read More >

The Best Practices and Advantages of Designing Effective Test Cases

The Best Practices and Advantages of Designing Effective Test Cases OverviewTest case is a &ldq...

Read More >

Quick Understanding on Stateful Sets in Kubernetes

Stateful sets are similar to deployments, they can scale up and scale down, they can perform rolling...

Read More >

Connect apps and integrate data with workflows using Azure Logic Apps

Implementing complex business process has been made easy. Logic Apps in azure provide a way to imple...

Read More >

SQL Server Data Tools (SSDT)

SQL Server Data Tools (SSDT) is a modern development tool for building SQL Server relational databas...

Read More >

Automate your workflow through GitHub Action

In this Blogs, We will go through the basics of GitHub Actions and how to make your own custom workf...

Read More >

Share

Try DevOpSmartBoard Ultimate complete Azure DevOps End-to end reporting tool

Sign Up

  • Recent
  • Popular
  • Tag
Tags
Monthly Archive
Subscribe
Name

Text/HTML
Contact Us
  • *
  • *