In the last article I wrote on this subject, we talked a bit about the Create Portal Content wizard. In that article, we walked through creating a list of leads that displays on the portal. Anyone can access the list, and it’s read-only. So where can we go from here?

I was doing some testing for my previous blog where I needed to repititively change the status of service request to Resolved, which will send a message to the citizen. I was thinking what if there is a way through which I am able to change something in the D365 very easily. What if I ask the bot to do it for me ?

There’s been lots of talk about the new portal management capabilities in the latest release of Dynamics 365 and portals. Managing content and adding web pages in portals has up until now been most easily done using the front-side editor when it comes to standard content; meanwhile adding views or forms for other non-portal entities has always been a manual process involving creating entity forms and entity lists on the CRM backend. Indeed, the pain and confusion involved with the process of doing so has been a big blocker in terms of adoption of the Portals as a turn-key solution.

We ran into a problem after updating to Microsoft Portal 9.0.6.7 and had to do some digging around to find the root cause. We captured our learnings and are sharing them here for anyone who runs into a similar issue.

Like many companies, part of our sales strategy is to respond to RFPs, and one of the recurring questions is, “What happens to us if your company/product is bought/sold?”. Adoxio has a great answer to this - we are a case study for how to support clients all the way through the product lifecycle, whether we own it or not.

Many regulatory organizations still have applicants fill out and submit paper forms at a general collection point, which are then manually sorted and distributed to the appropriate department. With all the licenses and applications that now govern society, how is it that the technology supporting this entire industry has not evolved with the times?

For those who work in regulated fields, the pain of obtaining a license through an agency is all too familiar. The long lines, the endless forms, and the total black hole of information while waiting for approval or rejection make for a difficult, hard to navigate experience for applicants. It’s also a terrible process for those who actually handle license and permit applications – the regulatory employees. On the other side of the counter, employees deal with an application management process that has not advanced much in the last 20 years.  Let’s look at three factors that make life more painful for regulatory employees: disparate systems, repetitive tasks, and dealing with complaints from the public.

Web templates are extensively used to render web pages for Dynamics 365 Portals. They make use of an ACE editor that allows users to write the necessary code to display data using Liquid and to control the appearance and behavior of html elements with CSS and JavaScript.

The ACE editor used by web templates does the job, but for a tool that is being used as frequently, it could use some modifications to provide a better user experience.

The Enhancements made to the ACE editor that we describe in this article try to improve its user interface with two main goals in mind: 1.Increase the area used for writing code and 2.provide a customizable and personalized color scheme.

If you have used Dynamics 365 you must be familiar with the + New button on the lookup. This enables the user to create a new item instead of selecting an existing one.

This feature has been a frequent ask for Dynamics 365 Portals. The good news is that this functionality was added by the product team a few releases back. The bad news is that it is only partially done.

In this post I’ll discuss Data Integration using Azure Logic App Service, we will create a Logic app that gets triggered when a case is created in Dynamics 365 and inturns creates a work item in Visual Studio Team services for the team to work on.

Logic App workflow is built using series of actions and Connectors, and has its own JSON based workflow definition schema, for details refer to my blog on The Basics of Azure Logic Apps Schema and Codeview editing