PL 400 : implement a Dataverse listener for an Azure solution (Publish and consume events)

Microsoft Dataverse is a tremendous product in the cloud market as it provides a business database with many features of applications that can consume software as a service (SaaS). We have already discussed about many features regarding this product, but it also integrates easily with external systems. Azure Bus Service provides the ability to work as asynchronous with the message broker and also facilitates to develop listener applications that can receive these events and processes as per the business requirements.

Microsoft Dataverse events trigger the execution of a remote code component called the listener.

These integrations are intended to provide an easy way to use additional extensibility outside the Dataverse platform. An Azure Solution Listener application that can read and process Microsoft Dataverse messages posted to the Azure Service Bus. A message queue is a store of messages on a service bus endpoint and a queue listener is an application that reads and processes these queued messages. Microsoft Dataverse supports a variety of methods to consume Azure Messaging Service Bus queue messages; queue, one-way, two ways, or REST. if using two way and REST, we are able to return a string of information back to Dataverse.

Write a queue listener:


  • Create a C# Console Application in Visual Studio that targets .NET 4.6.2 or higher.

  • Add the following NuGet packages:
    • Azure.Messaging.ServiceBus
    • Microsoft.CrmSdk.CoreAssemblies
  • In the application's Main method, paste the following code. Replace the Endpoint URL with your Azure Service Bus Namespace's Endpoint URL and the queue name if it differs:
string connectionString =@"[ENDPOINT URL]";
string queueName = "mslearnsamplequeue";
QueueClient queueClient = QueueClient.CreateFromConnectionString(connectionString, queueName, ReceiveMode.PeekLock);

  • To consume your message, use the "OnMessage" method, which provides the ability to process a Service Bus queue message in an event-driven message pump. 

queueClient.OnMessage(message =>
            {
                //get RemoteExecutionContext based on Message Format
                RemoteExecutionContext context = null;

                if (message.ContentType == "application/msbin1") //.NETBinary Message Format
                {
                    context = message.GetBody<RemoteExecutionContext>();
                }
                else if (message.ContentType == "application/json") //JSON Message Format
                {
                    context = message.GetBody<RemoteExecutionContext>(
                                      new DataContractJsonSerializer(typeof(RemoteExecutionContext)));
                }
                else if (message.ContentType == "application/xml") //XML Message Format
                {
                    context = message.GetBody<RemoteExecutionContext>(
                        new DataContractSerializer(typeof(RemoteExecutionContext)));
                }
                try
                {
//serialize the entire context leveraging the SerializeContext extension method
                    Console.WriteLine(context.SerializeContext());
                }
                catch (Exception ex)
                {
                    Console.WriteLine(ex.ToString());
                }
            });
  • At last we need to add Console.ReadLine() to our main method to allow for multiple messages to be processed.
  • run the application

Courtesy:


Comments

Post a Comment

Popular posts from this blog

PCF vs. Web Resources: Choosing the Right Extensibility Tool for Dataverse

Image
Extensibility refers to the ability to be extended or augmented beyond the default capabilities of the platform. This involves customization but also includes more advanced techniques, such as coding, integration with external services, and the use of custom components. In the context of Power Platform and Dynamics CRM, the term "extend behavior" refers to the ability to customize and extend the functionality of the platform to meet specific business needs. Extensibility often requires technical skills, such as coding in JavaScript, C#, or using tools like Azure Logic Apps and Power Automate for complex integrations. Customization  is a subset of extensibility. Customization involves configuring and modifying existing elements within the platform to suit specific business needs. Extensibility, on the other hand, covers a wide range of functions and techniques, including customization and more advanced development and integration tasks, to extend the capabilities of the Power
Read more

Is Debt Prosperity or Trap?

 “What can be added to the happiness of a man who is in health, out of debt, and has a clear conscience?”  Adam Smith Grandfather Bhishma lay on the bed of arrows and was preaching the future king of Hastinapur about political science, economics and the duties of the king. He took a deep breath and told Yudhishthira " Fire, debt and enemies must be dealt with quickly and completely. If there is any balance left, they can continue to grow. " The future king was listening with curiosity and was eager to learn about the complete knowledge from his grandsire. Each moment was important as the sun was moving from south to north. Either we read the quote of the father of modern economics or both ancient great scholars are advising to avoid debt. But the whole of modern economics is based on the debt that advises the public to borrow money. The aggressive campaign of banks and financial institutions has been luring more and more loans. Even democratic governments and public banks con
Read more

Exam PL-400: Microsoft Power Platform Developer

 Create a technical design (10-15%) Validate requirements and design technical architecture design and validate the technical architecture for a solution design authentication and authorization strategy determine whether you can meet requirements with out-of-the-box functionality determine when to use Logic Apps versus Power Automate flows determine when to use serverless computing, plug-ins, or Power Automate determine when to build a virtual entity data source provider and when to use connectors Design solution components design a data model design Power Apps reusable components design custom connectors design server-side components Describe Microsoft Power Platform extensibility points describe Power Virtual Agents extensibility points including Bot Framework skills and Power Automate flows describe Power BI extensibility points including Power BI APIs, custom visuals, and embedding Power BI apps in websites and other applications describe Power Apps portal extensibility points incl
Read more