Dynamics 365 Portals
Dynamics 365 Portals offer a great way to enhance customer experience by extending some CRM configurations directly to the customer. There comes a time when you may want your portal to perform some action that is beyond the out-of-the-box functionality.
Dynamics 365 Portals
Portal configuration can be a big undertaking, with many different Dynamics records that make up just one portal web page. What are Web Templates? Entity Forms? Entity Form Metadata? All of these record types and more are needed to build a Portal Web Page, and together they act as the structure to your portal.
As organizations tighten down their security, Multi-Factor Authentication (MFA) is becoming more and more common. MFA has it's drawbacks, however; as developers and administrators will find it more difficult to connect their apps to Dynamics 365 using an MFA enabled user.
Suppose you have a set of Yes/No fields, and you wanted to count how many of those fields were marked "yes." This can be accomplished easily by using a workflow with the Increment By Operation in Dynamics 365.
Here, we have a custom entity with 5 Yes/No fields.
Dynamics 365 portals offer a great way to provide data to your customers, but sometimes the portal can be a bit slow. Portals rely on data caches from Dynamics 365. That cache can be stale, and can cause a discrepancy between what is displayed in Dynamics 365 and the portal.
Do you plan on creating an entity with hundreds of fields? Were you told that you will hurt user-adoption and ease of use? Are you planning on doing it anyway? Great! But be cautious, because there are different limits on the amount of fields that can be added to an entity in Dynamics 365. There is currently no way of seeing these limits in Dynamics 365 before you reach them.
Suppose you want to move data between records that are not directly related, but share a common parent. Beringer Technology Group's Decimal Field Copy custom workflow can dynamically move values between records like these.
The image above represents a common set of relationships in CRM. Child A and Child B records belong to two separate entities and have no direct relationship, but they both lookup to the same parent record.
There comes a time when the needs of a CRM System outpace the out of the box functionality of Dynamics 365. While Dynamics 365 provides a vast framework from which one could build highly customized solutions for a variety of users, there may come a time when custom plug-ins are required to meet the needs of an organization.
What is a calculated field?
Calculated fields perform calculations using data from other fields and return the result. Calculated fields do not require knowledge in programming and are easy to set up.
Let’s start by creating some fields.
Create 2 fields and set the Data Type to Decimal Number and the Field Type to Simple.
A few hundred custom fields, another hundred or-so workflows, and twenty tabs; all for one form? Sounds like you’re building an XRM. The term “XRM” refers to an extension of a CRM that encompasses business processes beyond the typical sales, service and marketing oriented systems.