Tagging is common requirement in Dynamics CRM. Accounts can be tagged against multiple types. Contacts can be tagged for multiple interests.
Created a solution using PCF that makes tagging quick and intuitive. No more doing searching and linking tags using lookups. Just *click on* *click off*. Data goes in a related many to many association. Below is a demo of the Tagger.
This article shows how to present CRM data in a chronological timeline format. Timeline is best suited for those entities which have one or more date field in them. For example – Task, Work Orders, Inspections, Resource Bookings, etc.
Task has a start date and end date. The GIF below shows how a task timeline can be displayed inside Dynamics 365 using the PowerApps Control Framework.
Key notes about the footage below
- There are 7 tasks with start date and end date.
- Initially All Tasks views shows information in tabular format.
- Then Task Timeline view shows the same information in Timeline format.
- It is easy to visualise overlaps of tasks and other chronological details which get lost in the tabular view.
- On hover, it shows the start date and end date
- Lot more can be done onClick, onDrag, etc. but for now just a basic sample.
The code is on my Github.
PowerApps Component Framework can be used to transform the visual representation of CRM data (which was earlier restricted to only forms and views) into a more sophisticated and intuitive user experience.
This blog explores how a bland CRM view can be turned into a control of graphical nature that makes information more palatable to the visual cortex.
The scenario we have is an entity called Ratings which stores ratings for various venues in Canberra.
- We want to show the verified Ratings in green, while the unverified in blue.
- The layout should render the smaller fields on the left (stacked top to bottom).
- More descriptive fields like Review Comments should utilise lion’s share of the real estate towards the right.
Once the control is built and deployed to Dynamics, it can be easily consumed by your view designer using the View Customisations > Custom Controls section as shown below
Upon publish, you are able to represent the information in ways that were not possible before and meeting the three requirements outline above.
And yes, this is the same Dynamics 365 CRM’s typical view which we use everyday. So custom controls have answered the call to a more intuitive UX design.
The source code used to create this datacard has been published here
Note: PowerApps Component Framework is still in Preview, so not recommended for Production at the moment.