A Read-Only Grid can only always provide you with a static view of data. At times, it’s important to visualize some data in Dynamics 365 which offer more than just columns.
In most common scenarios, your custom records / customizations might have Start End Dates which is better viewed in a visual way. Here’s where Calendar Control comes into play –
Normally, below is how you visualize your data in Dynamics 365 where you have Start Date and End Date –
- As you can see, the data looks like in any other entity you’d design.
Here’s how you can enable the Calendar Control to change the View in question into Calendar Control –
- Go to the Entity/Table itself and click on Controls.
- Then, look for Calendar Control in the View.
- Then, configure the Start Date, End Date, Description, Duration fields.
And also make sure the selection is on the Calendar Control itself
- Once you save and publish the changes, let’s see how the control looks like.
Viewing Data in Calendar Control
Now that all the customization are published, here’s what the Calendar Control will look like –
- If you refresh, you’ll see the same in Calendar Control and not the Read Only grid.
- Also, you can switch between Day/Week/Month view
- If you click on any of the records, you’ll see the details of the record.
- And this will open the record itself.
Switching to Read-Only View
Since the default is now set to the Calendar View, you’ll need to switch it back to Read-Only.
- Look for the 3 ellipses or you might just see the View As button on the ribbon already.
- And select Read Only.
- And you’ll see the default shown
Hope this was useful!
Here are some Power Automate posts you want to check out –
- Select the item based on a key value using Filter Array in Power Automate
- Select values from an array using Select action in a Power Automate Flow
- Blocking Attachment Extensions in Dynamics 365 CRM
- Upgrade Dataverse for Teams Environment to Dataverse Environment
- Showing Sandbox or Non Production Apps in Power App mobile app
- Create a Power Apps Per User Plan Trial | Dataverse environment
- Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
- Co-presence in Power Automate | Multiple users working on a Flow
- Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
- Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
- Call a Flow from Canvas Power App and get back response | Power Platform\
- FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
- Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
- Asynchronous HTTP Response from a Flow | Power Automate
- Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
- Converting JSON to XML and XML to JSON in a Flow | Power Automate