Replace OOB Business Closures with a Custom Web Page in Dynamics 365 CRM - CloudFronts

Replace OOB Business Closures with a Custom Web Page in Dynamics 365 CRM

Posted On August 19, 2025 by Richie Jacob Posted in  Tagged in

Dynamics 365 CRM provides an Out-of-the-Box (OOB) Business Closures feature to define non-working days across your organization. However, in many real-world scenarios, we often face limitations with the default interface in terms of customization, UX/UI control, or extensibility.

In this blog post, I’ll Walk you through how you can replace the OOB Business Closures using a custom HTML + CSS + JavaScript web page embedded in Dynamics 365. This custom page will interact with a custom Dataverse table that stores your closure dates and related details.

Why Replace the OOB Business Closures?

Some of the common limitations of OOB Business Closures:

  • -Cannot add custom fields like “Reason”, “Department”, or “Applicable Teams”
  • -Limited UI customization (e.g., calendar picker, recurring closures)
  • -No direct integration with custom scheduling logic
  • -Not easily extendable for multi-region closure handling

What We’ll Build

A custom web resource embedded in a Dynamics 365 CRM dashboard or form tab that:

  • Lists existing business closures
  • Allows users to add new closures via a form
  • Uses Dataverse table (e.g., new_businessclosure) as the backend

Step-by-Step Implementation

1. Create a Custom Table in Dataverse

  • Name: Business Closures
  • Schema Name: new_businessclosure
  • Fields:
    • new_name (Text)
    • new_startdate (DateTime)
    • new_enddate (DateTime)
    • new_reason (Multiline Text)
    • new_region (Choice / Text)

2. Create the HTML Web Resource

3. Upload as Web Resource in CRM

  • -Go to Advanced Settings > Web Resources
  • -Upload the file businessclosures.html
  • -Add it as a web resource in the sitemap as a webpage url (like the main form for Settings or a Custom Entity)

Benefits of this Approach

– Fully customizable UI
-Supports additional metadata (reason, region, team)
-Extensible for APIs, workflows, Power Automate, etc.
-Better UX for users with real-time interactivity

To conclude, by using a simple HTML, CSS, and JavaScript front end, we can extend Dynamics 365 CRM to manage business closures in a much more flexible and modern way. It not only overcomes the limitations of the OOB feature but also gives us complete control over the user experience and data model.

I hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com.


Share Story :

SEARCH BLOGS :

FOLLOW CLOUDFRONTS BLOG :


Secured By miniOrange