Light Sepia Dark 01Summary A global product certification institute needed to know one thing reliably before it could issue a certificate: does this legal entity have a valid, executed certification agreement that covers this certification type and standard version, on this date. Answering that meant opening a signing platform, a document store, and a legacy CRM, then trusting somebody’s judgement. We built an Agreement Manager in Microsoft Dataverse that answers it with a query. The design decision that shaped everything else was refusing to rebuild what already worked. Adobe Acrobat Sign for Microsoft Dynamics 365 remains the signing engine. Azure Blob Storage remains the evidence store. The custom Dataverse layer exists only where the institute needs business control that neither provides: requirement rules, signer preparation, legal party snapshots, structured validation, and above all a machine readable record of what an executed agreement actually covers. This first part covers the foundation: eleven tables, the ownership boundary between Dataverse and Adobe, the coverage model that makes certification gating possible, and the alternate key strategy that prevents two active coverages from ever existing for the same scope. Part 2 covers the automation built on top, and is honest about the one piece that is missing. 02In This Blog A practitioner view of designing the data layer for certification agreement execution on Dataverse, where the output is not a signed PDF but a queryable statement of coverage. The Scenario: Certification decisions were being made without a reliable way to confirm that a valid agreement covered the applicant, the certification type, and the standard version in question. The Approach: Keep Adobe as the signing engine and Azure Blob as the document store. Build custom tables only where business control is genuinely missing. The Action: Eleven tables across a configuration layer, a process layer, and an evidence layer, with parental relationships on every snapshot child and eight alternate keys. The Outcome: Certification logic checks one thing, Agreement Coverage, and never inspects Adobe status or the existence of a PDF. The deliverable of a contract system is not the signed document. It is the ability to prove, in a query, that the document applies. Table of Contents 01Summary→ 02In This Blog→ 03Business Challenges→ 04The Build Boundary→ 05The Data Model→ 06Lifecycle and Duplicate Prevention→ 07Impact→ 08Conclusion→ 09FAQ→ 10Get in Touch→ 03Business Challenges The institute certifies products against a published standard. Before a certificate can be issued, the applicant’s legal entity must have signed the applicable certification agreement, and the agreement that applies depends on region, country, certification type, standard version, and the date the requirement became mandatory. Coverage was a human judgement. Confirming that a signed agreement actually applied to a given application meant reading a PDF and deciding. Two reviewers could reasonably reach different conclusions. Evidence was spread across systems. Executed agreements existed in a legacy CRM, in Adobe outputs, in a document generation tool, and in a manual register. No system held all of them. Requirement rules lived in people’s heads. Which template version became mandatory for which region and certification type, and from what date, was tribal knowledge rather than configuration. Duplicate active agreements were possible. Nothing prevented two concurrent active agreements for the same legal entity and scope, which makes the question of which one governs unanswerable. Manual and wet signature cases had no controlled path. Exceptions were handled by email and stored wherever the handler chose. The recurring failure is not that signing was hard. Adobe already did signing well. The failure was that nothing downstream could consume the result of signing as data. The trap we avoided The obvious move is to build a full contract lifecycle management suite: clause libraries, redlining, negotiation workspaces, a generic multi provider signing framework. All of that was explicitly ruled out of scope. None of it would have answered the coverage question, and each piece would have duplicated something Adobe or Dataverse already provides. 04The Build Boundary Before a single table was created, the specification fixed which system owns what. This is the decision that kept the build lean, and it is worth stating explicitly because it is the one most projects get wrong. Figure 1: The ownership boundary. Seven tables that a generic contract design would have created were deliberately not built. The rule applied throughout was simple. If a requirement can be met by supported Adobe managed functionality without losing business traceability, use the Adobe functionality. Custom tables exist only where the institute needs control that no product provides. Reuse before you extend The environment already contained reference tables for legal entity, region, subregion, country, certification type, standard version, and certification standard scope. Every one of those is referenced by lookup rather than recreated as a local choice. A choice column for country in a certification system is a data quality incident waiting for a rename. 05The Data Model Eleven tables were built in a strict order, and they fall into three layers with different ownership models. Configuration tables are organization owned because they are administered centrally. Process tables are user or team owned because they carry work. Evidence tables are organization owned because coverage is a fact about the institute, not about a user. Figure 2: The eleven table model in three layers, with the reference tables that were reused rather than recreated # Table Purpose Ownership 1 Agreement Type Reusable agreement categories Organization 2 Agreement Template Version Approved legal template and its Adobe workflow reference Organization 3 Agreement Role Definition Signer, reviewer and counter signer roles per template version Organization 4 Agreement Requirement Policy Configurable rule for when an agreement is required Organization 5 Agreement Request Central process record for preparation and lifecycle User or Team 6 Agreement Party Legal parties bound by the agreement, held as snapshots Parented to Request 7 Agreement Recipient Actual signers and their status snapshots Parented to Request 8 Agreement Document Metadata and control record for Blob stored files Parented to Request 9 Agreement Coverage Machine readable evidence that an executed agreement applies Organization 10 Agreement … Continue reading How a Sustainability Certification Nonprofit Automated Certification Agreements in Microsoft Dataverse with Full Audit History →

Global energy service providers operate across multiple jurisdictions, currencies, and regulatory regimes. This complexity demands precision in financial reporting and transparency in profitability analysis. Achieving reliable site-level profitability in such an environment requires a holistic architectural approach to financial consolidation rather than incremental fixes or tactical workarounds. Legacy State Challenges Strategic DecisionThe organization implemented Dynamics 365 Finance & Supply Chain as a unified financial backbone, replacing legacy IFS systems and spreadsheet-driven workflows. This decision was accompanied by a critical architectural trade-off: moving away from locally customized, entity-specific account structures toward a single, global Chart of Accounts (COA). Benefits of Standardization Unified COA StructureThe global COA was standardized using a 1000–6000 series: This created a common financial language across the organization, enabling both global consolidation and local statutory compliance. Engineering Derived Dimensions for Data Integrity Standardizing accounts alone was insufficient to achieve granular profitability visibility. The architecture required a mechanism to enforce dimensional consistency and eliminate manual errors. Derived Dimension FrameworkFive core dimensions were defined: Segment, Sub-Segment, Region, State, and Site. System Integration Operational Customization From Static Spreadsheets to Dynamic Power BI Dashboards Legacy Reporting Modernized Workflow Reporting Model Operational Cadence Frameworks Proof and Metrics Step-by-Step Implementation Playbook FAQs a. How do you handle different fiscal years?The system supports reporting for both January–December and April–March fiscal calendars to meet diverse statutory requirements. b. Can we track unbilled revenue?Yes. Project Management modules track planned versus actual work, allowing finance teams to post and reverse accrued revenue monthly. c. What happens if a site selects the wrong dimension?This risk is mitigated through derived dimensions, which automatically populate dependent dimensions based on the selected Site code. To conclude, this architecture not only addresses immediate challenges but also positions the organization for long-term sustainability. It enables leadership to make informed decisions based on reliable, timely data, while ensuring compliance across diverse regulatory environments. Ultimately, the shift represents a move from reactive financial management to proactive, strategic control-delivering clarity, accountability, and resilience across global operations. Connect with CloudFronts to get started at transform@cloudfonts.com

Marketing teams have always produced a steady stream of content, blogs, case studies, and articles. While this content captures valuable insights, it often tells only part of the story. Most blogs focus on technical implementations and how the work was executed, rather than clearly articulating the business problem, transformation process, and measurable outcomes. As a result, the overall impact created often remains in the background. Marketing team at CloudFronts started noticing a few consistent patterns: The issue was not a lack of knowledge or expertise. Our teams had deep experience. The real challenge was that customer insights were spread across different team members, and marketing did not always have a structured way to capture the full journey. That is when we started rethinking how we can capture the customer Journeys. The Challenge with Traditional Customer Content In every customer project, valuable knowledge exists across multiple roles. However, marketing rarely has direct access to all these perspectives at the same time. Without a structured process to capture insights across teams, much of the content tends to focus on technical implementation, since delivery teams are best positioned to describe how the solution was designed and implemented. While these blogs are useful, they often miss the broader story: For decision makers evaluating partners, this business context is often more valuable than the technical details alone. Recognizing this gap pushed us to rethink our content process. Our Shift: Turning Customer Insights into Strategic Content Instead of relying on ad-hoc blog contributions, we introduced a structured customer Journey capturing process. The process starts with something simple but powerful: a conversation with the delivery team. For every major customer engagement, marketing team schedules a dedicated discussion with the people who were directly involved in the project. This usually includes architects, consultants, project manager, and sometimes presales. During these sessions, we guide the conversation using a structured set of questions designed to uncover the full customer journey. We focus on areas such as: In many cases, the delivery team also walks us through the system they implemented. Seeing the solution in action helps marketing understand the practical value delivered to the customer. These discussions capture something that traditional documentation often misses: the real story behind the transformation. Building an AI-Powered Customer Knowledge Base Capturing the conversation is only the first step. The real transformation in our process begins when we introduce AI. We record and transcribe these discussions and combine them with existing project documentation, including: We then bring all this information into AI-powered tool called NotebookLM, creating a dedicated knowledge repository for each customer journey. Instead of navigating through multiple documents and scattered notes, marketing team now has one structured knowledge base containing the full project story. This changes how we approach content creation. Using AI to Identify the Best Blog Ideas Once the knowledge base is built, we use AI to analyze the information and help us identify the most meaningful narratives within the project. Our goal is not simply to generate blogs automatically. Instead, we use structured prompts to help AI discover the strongest story angles hidden within the customer journey. This helps us uncover ideas such as: Instead of producing just one blog from a customer project, we often identify multiple content opportunities from a single engagement. Moving Beyond Technical Blogs This new approach has significantly changed the type of content we create. Rather than publishing isolated technical blogs, we now build a structured content ecosystem around each customer story. This includes: Customer Journey Blogs A narrative that captures the full transformation from the business challenge to the final outcomes. Use Case Blogs Detailed articles explaining how specific solutions solved operational challenges. Customer Milestone Stories Updates on key project achievements such as major implementations, go-lives, and expansion phases. In essence, one customer engagement now supports multiple layers of storytelling. Why AI Matters for Modern Marketing AI is often discussed as a way to generate content faster. In our experience, its real value is different. AI helps us access knowledge that already exists within the organization but is often difficult to gather and use effectively. Every customer project generates a significant amount of insight: Without the right tools, much of this knowledge remains buried in documents, presentations, and internal meetings. AI allows us to analyze, connect, and transform this knowledge into meaningful stories. The Future of Customer Storytelling Through this process, we see marketing evolving beyond content production. Our role increasingly becomes the bridge between delivery expertise and market insight. By capturing customer journeys, organizing knowledge, and using AI to uncover meaningful narratives, we are moving from fragmented content creation toward intentional storytelling. In a market where decision makers want partners who truly understand their challenges, authentic customer stories carry far more weight than generic marketing messages. The organizations that stand out will not necessarily be the ones producing the most content. They will be the ones that capture and communicate the stories that truly matter. To conclude, in today’s market, decision-makers are not looking for generic content.They are looking for partners who understand their challenges and can prove impact. The organizations that stand out will not be the ones producing the most contentbut the ones telling the most meaningful, authentic customer stories. And with AI, we now have the ability to do exactly that at scale, with precision, and with impact.

An Australia-based linen manufacturing and distribution company was using Microsoft Dynamics 365 to manage their sales lifecycle. Their sales process included: The issue arose when sales representatives needed to add multiple existing products to an Opportunity. The Real Problem Out-of-the-box behavior in Dynamics 365 allows users to: While this works functionally, it becomes inefficient for organizations managing: This resulted in: The business requirement was clear: Users should be able to select multiple existing products and create Opportunity Product records in bulk, from a single interface. Architectural Decision Instead of: To address this, we introduced a custom button on the Opportunity Products subgrid. When clicked, it opens an HTML web resource that allows users to select multiple existing products in a single interface. The selected products are then processed through a Custom Action, which handles the bulk creation of Opportunity Product records server-side. Why Use an HTML Web Resource? In Microsoft Dataverse, not every customization belongs directly inside the main form. Sometimes we need: HTML Web Resources allow us to build: Without disturbing the standard CRM experience. The Web Resource We created an HTML web resource named: The HTML web resource renders a searchable grid of existing Product records, allowing users to perform multi-selection. The selected product IDs are then passed to a Custom Action, which handles the creation of related Opportunity Product records against the active Opportunity. Opening the HTML Web Resource from the Subgrid Button The key technical step was opening the HTML page when the custom ribbon button is clicked. We used modern navigation APIs. JavaScript Used on the Ribbon Button How This Works When the custom button is clicked, the script first retrieves the current Opportunity record ID. This ID is then passed as a parameter to the HTML web resource so that the selected products can be associated with the correct Opportunity. The web resource is opened as a modal dialog using the target: 2 navigation option, ensuring that users can complete the bulk selection process without leaving the form. Inside the HTML Web Resource Within the HTML web resource: This design ensures: All without navigating away from the form. How This Approach Saved Time Faster User Workflow Users select multiple products in one screen. Clean Architecture Concern Where It Lives Business Data Dataverse UI Interaction HTML Web Resource Batch Logic Custom Action (C# Plugin) To encapsulate, with this design the Client was able to: Opening an HTML Web Resource from a button in Microsoft Dynamics 365 is a powerful extension technique. It allows organizations to: We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

We are delighted to announce that Gouge Linen and Garment Services Partners with CloudFronts for the implementation of Dynamics 365 Sales and Customer Services.  Founded in May 1945, Gouge Linen and Garment Services is a leading 100% Australian-owned industrial laundry provider, strengthening its role as a trusted partner across healthcare, aged care, hospitality, manufacturing, and food production sectors. Backed by state-of-the-art facilities and a dedicated logistics network, the company delivers high-quality linen, garment, mat, and towel services with exceptional reliability and efficiency. Gouge remains committed to sustainability through advanced water-saving systems, energy-efficient operations, and responsible business practices, reinforcing its strong reputation for service excellence and community impact.  Learn more about them at https://www.gouge.com.au/  Gouge Linen currently relies on excel-based quoting, manual freight costing, and fragmented data stored across ABS/Oracle BI. This lack of integration limits visibility across departments, creating inefficiencies, delays, and scalability challenges. CloudFronts will deploy Microsoft Dynamics 365 Sales with a CPQ (Configure, Price, Quote) process to automate quote generation, team to streamline sales, service, and route costing workflows. The solution will deliver real-time visibility into inventory, production costs, and freight data, enabling faster, data-driven decisions across the organization.   The implementation will reduce quote turnaround time from days to under an hour, improve coordination between sales, operations, and logistics teams, and enhance overall customer experience.  On this occasion, Priyesh Wagh, Practice Manager at CloudFronts, stated:  “ We look forward to partnering with the Gouge team as we initiate the first phase of their Dynamics 365 Sales and Customer Service implementation, which will evolve into a comprehensive quotation engine. This initial rollout will establish a strong foundation for an integrated sales-to-service platform, with the potential to extend into billing capabilities in the future. We’re excited to collaborate with the Gouge Linen and Garment Services team on this transformation journey.” About CloudFronts  CloudFronts is a global AI- First Microsoft Solutions & Databricks Partner for Business Applications, Data & AI, helping teams and organizations worldwide solve their complex business challenges with Microsoft Cloud, AI, and Azure Integration Services. We have a global presence with offices in U.S, Singapore & India.    Since its inception in 2012, CloudFronts has successfully served over 200+ small and medium-sized clients all over the world, such as North America, Europe, Australia, MENA, Maldives & India, with diverse experiences in sectors ranging from Professional Services, Financial Services, Manufacturing, Retail, Logistics/SCM, and Non-profits.     Please feel free to connect with us at transform@cloudFronts.com 

Resource Management is at the heart of delivering successful project-based services. In Dynamics 365 Project Operations (D365 PO), it ensures that the right people with the right skills are assigned to the right projects at the right time. Effective resource management boosts utilization, enhances profitability, and drives customer satisfaction. This article explores how D365 PO supports resource allocation, capacity planning, and skills-based matching. 1. Resource Types in D365 PO In D365 PO, resources can be: Resource Type Description User Licensed individual within the system Contact External personnel (e.g., subcontractors) Generic Placeholder resource for planning purposes Resources are linked to roles, organizations, cost rates, and sales prices. 2. Resource Allocation  Process: Booking Types: Each booking is visible in Team Members section of the project and feeds into utilization reports.  3. Capacity Planning Capacity planning in D365 PO is about balancing project demands with available workforce capacity. Key Capabilities: Project Managers and Resource Managers can proactively manage staffing levels, avoiding burnout or bench time. 4. Skills-Based Matching Matching resources based on skills, proficiency, and certifications ensures project quality and client satisfaction. Skill Matching Features: This structured approach supports fair allocation, talent development, and project success. 5. Impact on Project Execution Good resource management: All bookings and allocations are tightly integrated with WBS tasks, time entry, and financial tracking modules in Dynamics 365 PO. 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.

We are delighted to announce that the largest US-based manufacturer of Fire-Rated and Architectural steel windows, Optimum Windows is partnering with CloudFronts for Managed Services Agreement (MSA) renewal.  Optimum Window, established in 1985, is a family-owned business based out of Ellenville, in upstate NY. Since then, Optimum Window has become the largest and most diversified manufacturer of Fire-Rated and Architectural steel windows in the United States and has continued its growth with a series of custom high-tech metal window and door systems designed for commercial, high-end residential & landmark applications. Learn more about Optimum Window at https://optimumwindow.com/   Optimum Window’s partnership with CloudFronts began with the implementation of a CRM system with custom enhancements that automates their end-to-end sales & order processes.  Under this MSA, CloudFronts will provide support & maintenance services for the system based on Microsoft Dynamics 365 Sales.  About CloudFronts  CloudFronts is a global AI- First Microsoft Solutions & Databricks Partner for Business Applications, Data & AI, helping teams and organizations worldwide solve their complex business challenges with Microsoft Cloud, AI, and Azure Integration Services. We have a global presence with offices in U.S, Singapore & India.    Since its inception in 2012, CloudFronts has successfully served over 200+ small and medium-sized clients all over the world, such as North America, Europe, Australia, MENA, Maldives & India, with diverse experiences in sectors ranging from Professional Services, Financial Services, Manufacturing, Retail, Logistics/SCM, and Non-profits.     Please feel free to connect with us at transform@cloudfronts.com 

In conversations with Business Central customers, one recurring theme stands out: permissions remain the single biggest operational pain point. For too long, organizations have taken the path of least resistance: The outcome? A fragile balance where security is compromised, efficiency is slowed, and compliance becomes an afterthought. But permissions should not be a roadblock. They should be a strategic enabler. Moving Beyond “Access” to “Enablement” Business Central has quietly matured its security model. The challenge is not capability, but mindset. Organizations must move from access as convenience to permissions as governance. Here are three levers that shift permissions from problem to advantage: Why This Matters for Leaders Strong permissions are not an IT housekeeping task—they are a strategic safeguard: The Leadership Imperative To conclude, Business Central leaders must stop viewing permissions as a technical nuisance. In an era of increasing scrutiny on data security and compliance, permission architecture is leadership architecture. The organizations that invest in this today will not only reduce risk but also unlock smoother onboarding, faster adoption, and a culture of accountability. If you need further assistance or have specific questions about your ERP setup, feel free to reach out for personalized guidance. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com. It’s time to replace the culture of SUPER users with a culture of super governance.

We are pleased to announce that the largest heavy-duty truck manufacturer in North America has partnered with CloudFronts for Phase 1 of a Dynamics 365 ERP implementation. The company is the largest heavy-duty truck manufacturer in North America and a leading producer of heavy- and medium-duty trucks as well as specialized commercial vehicles. Its Gastonia Components and Logistics facility plays a pivotal role in the supply chain, providing stamping, metal fabrication, and sub-assembly of cab and chassis components used across manufacturing operations and aftermarket support. Additionally, the facility oversees line sequencing of parts for manufacturing plants and aftermarket packaging, ensuring efficiency and consistency throughout the production process. The customer is facing several operational challenges due to disconnected systems and limited data visibility. The lack of real-time inventory insights is causing production delays, slowing down planning, scheduling, and work order releases. Teams are burdened with redundant work and manual effort, as legacy systems force them to navigate multiple platforms, leading to inefficiencies and errors. Procurement processes are also impacted, with limited visibility into raw material availability and purchase history resulting in material waste, overstocking, shortages, and purchasing delays.  Phase 1 focuses on implementing Dynamics 365 Supply Chain Management (SCM) to establish the client’s defined end-state capabilities. This phase includes configuring and setting up core business processes such as User & Security Management, Product Information Management, Warehouse Management, Procurement, and other operational setups, which will be further expanded in Phase 2.  On this occasion, Priyesh Wagh, Practice Manager at CloudFronts, stated:   “This engagement marks the beginning of an ERP implementation journey, laying the groundwork for long-term business transformation. At CloudFronts, we are committed to helping our client overcome their complex challenges through technology. By implementing Dynamics 365 Supply Chain Management, we aim to streamline processes, reduce inefficiencies, empower their team with data-driven insights, and build scalable capabilities for future growth.”  About CloudFronts  CloudFronts is a global AI First Microsoft & Databricks Solutions Partner for Business Applications, Data & AI, helping teams and organizations worldwide solve their complex business challenges with Microsoft Cloud, AI, and Azure Integration Services. We have a global presence with offices in U.S, Singapore & India. Since 2012, CloudFronts has empowered 200+ global clients small and medium-sized clients all over the world, such as North America, Europe, Australia, MENA, Maldives & India, with diverse experiences in sectors ranging from Professional Services, Financial Services, Manufacturing, Retail, Logistics/SCM, and Non-profits.   Please feel free to connect with us at transform@cloudfronts.com