You are currently browsing the category archive for the ‘Architecture’ category.

Case Study: you have a company site hosted on a CMS (let’s assume WordPress for the purpose of this). You want to capture inquiries from the public, and create Leads in your Dynamics 365 for Sales.

Technologies: WordPress site (you must be able to create plugins) or any other public site, Logic Apps, Dynamics 365 for Sales.

On your WordPress site you have a plugin that collects the Lead details and pushes then to a HTTP end-point. This is a JSON with a payload containing the Lead details. I’ll let the WordPress gurus figure this one out, but if you run a search for WordPress form to JSON plugin you will find several results of already existing plugins.

On your Azure Portal, find Logic Apps and create a new app. Once your app is created (it only takes a few moments), go into designer and create a blank Logic App. Search for HTTP and find HTTP Request.


Read the rest of this entry »

Ok, we all know by now, with Dynamics 365 CE we have portal capabilities. It’s a configurable portal driven by the config and data in your CRM. But that’s where I’ll stop. The CRM Portal architecture is very much coupled to your CRM, and it doesn’t qualify for our Decoupled Architecture topic.

Instead, in this post I want to focus on the large majority of enterprises. They already have a portal, most likely a CMS driving their current site, Read the rest of this entry »

As we’ve seen in the previous article, Decoupled Architecture is a model that allows various layers of a platform to execute independently, but interface together.

In this article I want to focus a little deeper, and tackle the Decoupled Architecture model when it comes to integrations.

Imagine this typical scenario:

Read the rest of this entry »

In this article I want to focus on Decoupled Architecture. This is the start of a small series, in the end driving the idea back to Business Applications, but this first post is going to be quite agnostic.

Very often we are faced with a project where, dues to obvious constraints, like time and budget, we have to produce an output that might not be ideal on the long run. While we’re solving the problem at hand successfully, are we really setting the customer on the right path for the future?

Let’s look at what Decoupled Architecture is in the first place.

This pattern enables layers to execute independently, but keep interfacing together.

Read the rest of this entry »

MVP Reconnect

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 617 other followers

Follow Dynamics 365 Wizardry on