Customer Insights: Rendering Marketing Form using React App

Have you ever used the default Customer Insights – Marketing Forms? If yes, you will notice that the default URL generated is random:

https://{server-load}/{organizationid}/digitalassets/forms/{msdynmkt_marketingformid}

In the eyes of us tech-savvy, we probably don’t really think of the URL as a problem. But, for the others, they might think that the URL is kind of fishy, and they can’t authenticate the owner of the URL. Luckily, Microsoft is allowing this page to be wrapped by another site, which will serve as the theme for today’s blog post (the GitHub repo is provided at the bottom of this post). Let’s learn!

Continue reading “Customer Insights: Rendering Marketing Form using React App”

Dataverse: Address 101

The bigger your Contacts/Accounts (Customers) data, the more it also consumes your Dataverse Database Capacity. I had a client who had a database overage problem, and further checking, the CustomerAddress table was on the list. If you open the table, you will find lots of empty addresses. Why is it so? Today’s blog post will try to unveil what, why, and how to solve this issue. Here is CustomerAddress (or Address) 101!

Continue reading “Dataverse: Address 101”

Dataverse: Create reusable C# Code/Custom API to bypass specific plugin steps

As a (lazy) Developer, I always find a way to implement something as simply as possible. The more experience that we are gaining over the years will eventually show us certain language features/components that can support it. For example, in today’s blog post, we want to create a feature where we want to bypass certain plugin steps that will be called from C# code (plugin, workflow, etc) and also Power Automate. So here is the implementation!

Continue reading “Dataverse: Create reusable C# Code/Custom API to bypass specific plugin steps”

Azure Data Factory: Read CSV file, Transform and push data to Dataverse

Let’s try to create a simple scenario that we can do in Azure Data Factory! Azure Data Factory is a serverless data integration service that sits in the Azure. The terminology of ETL (Extract, Transform, and Load) or ELT (Extract, Load, and Transform) can be processed by it, and there are lots of connectors (like Power Automate) to read from multiple sources and push the data into the destination.

For today’s scenario, we will do a simple scenario that utilizes Azure, self-hosted to take the Customers CSV file from Azure Blob Storage > transform the row into the needed format > push the data into Dataverse. FYI, as this is an exploration blog post, it might be the best “performance” yet, and I am open to suggestions.

Continue reading “Azure Data Factory: Read CSV file, Transform and push data to Dataverse”

Power Automate: Renew App Registration Client Secret and Update Dataverse Environment Variable Value

Last week, we learned how to create an email notification to remind us if App Registration in Azure expires. Today, we will learn how to apply automation to generate a New Secret and update the Dataverse Environment Variable. In the flowchart, here are the steps that we will do:

Today’s demonstration

Continue reading “Power Automate: Renew App Registration Client Secret and Update Dataverse Environment Variable Value”

Power Automate Custom Connector – Implement Retry Function, Azure Application Insights

Another journey on how to create a Power Automate Custom Connector with .NET API 8. Last week, we created a .NET API Project that implements the API Key for the Authorization process. Today, we will add more features including adding monitoring logs using Azure Application Insight and how to create an action where we can implement the retry function.

Continue reading “Power Automate Custom Connector – Implement Retry Function, Azure Application Insights”
Design a site like this with WordPress.com
Get started