Summary In rapidly evolving sales organizations, business requirements rarely remain static. New products, services, sales categories, commercial models, and operational scenarios can continuously introduce the need for additional values in Dynamics 365. For one of our clients, this resulted in a recurring dependency on the technical team. Whenever the business needed to add or modify values in a Dynamics 365 Choice column, they had to approach the implementation team for a seemingly small configuration change. At first glance, replacing the Choice column with a Lookup table appeared to be a natural solution. However, that approach would introduce a much larger change: migrating existing records, replacing references throughout the application, modifying system processes, reviewing integrations, and potentially impacting logic that already depended on the existing Choice values. Instead of redesigning the data model to solve a configuration problem, I approached the requirement from a solution-architecture perspective. I built a self-service Dataverse Choice Manager that allows authorized users to select a Dataverse table and Choice column, add or update options, publish the metadata, and automatically create an audit record and notify system administrators. The solution uses supported Dataverse Web API and Metadata APIs to perform controlled schema-level operations while introducing governance, auditability, and guardrails around those changes. The result is a model where the business can adapt its Choice values without continuously depending on developers, while the technical team retains control over security, governance, auditing, and platform integrity. Case Study Read more about our Journey with this Customer over here: View Case Study Table of Contents Introduction Business Requirement The Architectural Decision How I Solved It Implementation Procedure End-to-End Working Custom Auditing and Governance Working Within Dataverse Platform Boundaries Benefits of the Solution Limitations and Guardrails Conclusion Introduction Dynamics 365 implementations often evolve alongside the businesses they support. A sales organization may initially define a finite set of values for a Choice column. Over time, however, new products are introduced, sales processes change, new commercial categories emerge, and terminology evolves. The technical change may appear trivial: “I just need to add one more option to this Choice field.” But when the same request occurs repeatedly, a different problem emerges. The business becomes dependent on the technical team for configuration changes that are fundamentally part of day-to-day business evolution. For one of our clients, this pattern was becoming increasingly common. The organization is highly sales-focused and operates in an environment where business requirements continue to evolve. The question therefore became: Can I give the business controlled self-service access to Choice values without redesigning the existing Dataverse data model? Rather than immediately changing the schema, I looked at the problem from a solution-design perspective. The answer was to build a controlled metadata management layer over Dataverse. Business Requirement The client’s requirement was straightforward: Select a Dynamics 365 table. Select a Choice column. Add a new option when the business needs one. Update an existing option label when terminology changes. The challenge was not simply performing these operations. The challenge was performing them safely. A typical Dynamics 365 user does not need unrestricted access to the Dataverse schema. Giving users broad customization privileges would create an entirely different governance problem. I therefore needed to balance two competing objectives: Business agility The sales team should not need to raise a development request every time a new Choice value is required. Technical governance The organization still needs to know: Who made the change? What was changed? When was it changed? Which table was affected? Which Choice column was affected? What was the previous value? What is the new value? Was the change successfully published? This led us to a more important architectural principle: Self-service does not have to mean unrestricted access. The solution should expose only the operations that the business needs while keeping the underlying metadata APIs behind a controlled interface. The Architectural Decision Option 1: Replace the Choice with a Lookup One possible solution was to replace the existing Choice column with a Lookup pointing to a new Dataverse table. Conceptually, this would provide an excellent long-term model for highly dynamic business values. For example: Sales Record | +– Category Lookup | +– Category A +– Category B +– Category C +– Category D The business could then create new category records without changing metadata. However, the problem was the existing implementation. The Choice column was already being used across the solution. Replacing it would potentially require: Identifying all existing records containing the Choice value. Creating corresponding records in the new Lookup table. Migrating existing data. Replacing the existing field references. Updating JavaScript. Reviewing plugins. Reviewing Power Automate flows. Reviewing business rules. Reviewing integrations. Updating reports and Power BI dependencies. Testing existing processes. Deploying the changes across environments. In other words, a small configuration problem could turn into a substantial data-model transformation. The Architectural Conclusion The problem was not necessarily that the Choice column was the wrong data type. The problem was that the organization needed a controlled way to manage its values. Therefore, rather than redesigning the data model, I preserved the existing architecture and built a self-service management capability around it. How I Solved It I designed a web-resource-based application inside Dynamics 365: Dataverse Choice Manager Dataverse Picklist Manager. The application provides a simple interface through which an authorized user can: Select a Dataverse table. Retrieve the available Choice columns. Select a Choice column. Retrieve its existing options. Add a new option. Update an existing option. Publish the affected table. Generate an audit record. Notify the system administrator. From the user’s perspective, this becomes a simple business operation. From the platform perspective, however, the application is interacting directly with Dataverse metadata. The high-level architecture is: Dynamics 365 User | v Dataverse Choice Manager | +——————–+ | | v v Dataverse Web API Metadata Actions | | | InsertOptionValue | UpdateOptionValue | DeleteOptionValue | PublishXml | v Dataverse Metadata | v Choice Column Updated | +———————-+ | | v v Custom Audit Log System Administrator Email This is where the solution becomes more … Continue reading How a Texas-Based AI and Cybersecurity Services Company Streamlined Dataverse Choice Management in Dynamics 365 →

☼ Light ☶ Sepia ☽ Dark 01Summary During a recent Dynamics 365 implementation for a customer in the manufacturing industry, we came across a simple but important user experience requirement: when the Target Margin exceeded 45%, users needed to know about it and have an easy way to correct it. Rather than interrupting the user with a hard error or adding another button to the form, we used the native field recommendation control to provide guidance directly where the decision was being made. With a single click, the user can set the Target Margin back to 45%, trigger the field’s existing logic, and receive confirmation that the change was made. 02In This Blog This blog explores a simple but useful way to make Dynamics 365 forms more interactive using field recommendations. The Scenario: A Target Margin above 45% needs attention, but we don’t want to interrupt the user with a hard error. The Approach: Use the native Dynamics 365 field recommendation to place the guidance right where the user needs it. The Action: Give the user a one-click option to set the Target Margin back to 45%. The Outcome: Update the field, trigger its existing logic, and show a simple confirmation all without adding a new button, plugin, or complex customization. A small recommendation, a single click, and a much smoother user experience. Table of Contents 01Summary→ 02In This Blog→ 03Business Challenges→ 04Solution Overview→ 05Technical Approach→ 06Impact→ 07Conclusion→ 08FAQ→ 09Get in Touch→ 03Business Challenges Most teams that want to nudge a user on a specific field end up reaching for something heavier than the problem needs. A business rule can show an error or a warning, but it only fires on save or on change, and it cannot run a custom action when clicked. A ribbon button can call a script, but it sits at the top of the form, disconnected from the field it actually relates to. A form notification banner can carry a message, but it does not support a click handler, so it cannot open a dialog or call an action. None of these give a user a visual cue on the field itself that also does something when clicked, which is what teams ask for when they say ‘can we show a hint here and let them act on it’. The field recommendation control already exists in the platform for exactly this gap, but it is easy to miss because Microsoft’s own documentation covers the property, not the click through pattern most teams actually want. 04Solution Overview Dynamics 365 already ships a feature called field recommendations, the small lightbulb icon that can appear next to a field when the platform or a customization wants to draw attention to it. We set a recommendation on a field with a short message and a clickable action. When a user clicks the icon, the form runs a JavaScript function we registered against it. Here that function opens an alert, in a live rollout it can just as easily open a business process step, set a related field, or launch a quick create form. Why not a business rule or a ribbon button A business rule stops the user after they try to save or change the field. A ribbon button sits away from the field it concerns. The recommendation icon shows up on the field itself, before the user moves on, and it is the only one of the three that supports a click through action out of the box. 05Technical Approach Register the OnLoad handler (or trigger on any event)Add the JavaScript web resource to the form and bind a function to OnLoad, passing the execution context. Get the field controlInside the handler, call formContext.getControl on the target field. Attach the recommendationCall addNotification on that control with notificationLevel set to RECOMMENDATION, a message, a uniqueId, and an actions array pointing at the click handler. Handle the clickThe action function fires when the user clicks the icon. In this build it opens an alert dialog, nothing more. Clear it when resolvedOn the field’s OnChange event, check the condition and call removeNotification with the same uniqueId once it no longer applies. new_recommendation.jsjavascript function onLoad(executionContext) { var formContext = executionContext.getFormContext(); var attribute = formContext.getAttribute("cf_targetmargin"); if (!attribute) { console.error("cf_targetmargin attribute not found."); return; } attribute.controls.forEach(function (control) { control.addNotification({ messages: [ "The Target Margin must be below or equal to 45%, would you like to set the Target Margin accordingly?" ], notificationLevel: "RECOMMENDATION", uniqueId: "targetMarginRecommendation", actions: [ { message: "Set Target Margin to 45%", actions: [ function () { attribute.setValue(45); attribute.fireOnChange(); Xrm.Navigation.openAlertDialog({ text: "You have successfully changed the Target Margin to 45%.", title: "Target Margin Updated" }); console.log("Target Margin successfully set to 45%."); } ] } ] }); console.log("Recommendation added to: " + control.getName()); }); } Setting Value Event OnLoad and Field OnChange Library new_recommendation.js Functions onLoad, onDiscountChange Pass execution context Yes Field discountpercentage Form event registration ⚠Recommendations do not clear themselves addNotification puts the icon on the field and leaves it there until removeNotification is called with the same uniqueId. If a user fixes the value and moves on without an OnChange handler removing it, the lightbulb stays lit. We missed this in the first pass and had testers reporting a stuck icon that never went away. You can use multiple recommendations by linking them with unique IDs. This will help to handle multiple calls else there would be issue in adding, removing and calling functions. How this looks on the form. The bulb icon next to the field. Once user clicks to accept recommendation. Action is fired and makes the desirable changes. 06Impact 1web resource deployed 0plugins or workflows added 1 clickfrom field icon to custom action 40 linesof JavaScript in the handler The recommendation fires while the user is still on the field, not after they try to save. One JavaScript file replaced what would otherwise be a business rule, a ribbon button, and a separate form notification. 07Conclusion Field recommendations are a small, easy to miss control in … Continue reading How to Connect Dynamics 365 Field Recommendations to Custom Logic with One Click →

Summary Our previous article (Check out my previous blog here – Transforming Return Logistics for a USA Manufacturer: Automating Shipment Processing with Dynamics 365 Customer Service) covered how we integrated Dynamics 365 Customer Service with FedEx to automate the creation of return shipments for a USA-based manufacturer — solving the shipment-creation half of the requirement. But creating a shipment is only the start. Once a package leaves the customer, the business still needs to know what’s happening to it — has FedEx received it, is it still with the customer, or has it been delivered? Previously, agents answered this manually by checking the FedEx site case by case, which didn’t scale. The second phase closes that gap with a scheduled integration between Dynamics 365 Customer Service, Dataverse, Integration, and the FedEx Tracking API. It automatically identifies eligible Cases, pulls the latest FedEx tracking events, determines whether the shipment has entered FedEx possession, and updates the Case accordingly. The result is a closed-loop process: Create Shipment → Capture Tracking Number → Monitor Shipment → Detect FedEx Possession → Update CRM. This article covers how the integration was designed, how tracking events were interpreted, how Integration processes the API response, and the technical considerations involved in building against the FedEx Tracking API. Table of Contents From Shipment Creation to Shipment Visibility The Business Challenge Solution Overview Identifying Cases Requiring Tracking Calling the FedEx Tracking API Understanding FedEx Tracking Events Determining Whether a Shipment Has Been Tendered Updating Dynamics 365 Customer Service Handling Exceptions and Empty Tracking Responses Technical Architecture Designing the Integration Around Business Events Business Impact FedEx Tracking API Limitations and Guardrails Final Thoughts This Blog Explains Why shipment creation alone was not enough to complete the return logistics process. How Dynamics 365 Customer Service was connected to the FedEx Tracking API. How eligible Cases are identified automatically. How tracking events such as Dropped Off, Picked Up, and In FedEx Possession are interpreted. How the solution determines when a shipment should be considered tendered. How the latest tracking information is written back to Dynamics 365. How Integration handles API responses and exceptions. The limitations and throttling considerations of the FedEx Tracking API. From Shipment Creation to Shipment Visibility In the previous implementation article (Check out my previous blog here – Transforming Return Logistics for a USA Manufacturer: Automating Shipment Processing with Dynamics 365 Customer Service), the primary objective was to eliminate the manual process of creating FedEx return shipments. The customer service representative could initiate the shipment directly from the Dynamics 365 Case. The system handled the rest: Collect Case and customer information. Register the shipment with FedEx. Generate the return label. Capture the tracking number. Store the tracking number against the Case. Send the return label to the customer. That created a significant improvement in the shipment creation process. However, there was still a gap. The tracking number was now inside Dynamics 365, but the shipment status was still outside Dynamics 365. This highlighted an important principle in integration design: True integration goes beyond just creating data in an external system—its real power lies in closing the information loop. By including end-to-end shipment tracking, we ensure full visibility, proactive exception management, and a seamless experience from order creation to final delivery. The second phase therefore asked a different question: Once Dynamics 365 creates a shipment, can it also continuously understand what is happening to that shipment? The answer was yes. The Business Challenge The existing process (Before FedEx Intg. Was implemented) required customer service representatives to manually monitor return shipments. A typical workflow looked like this: Open Dynamics 365 Customer Service. Find the Case. Copy the FedEx tracking number. Open the FedEx tracking website. Enter the tracking number. Enter the tracking number. Review the latest shipment event. Review the latest shipment event. Determine whether the package had been handed over to FedEx. Return to Dynamics 365. Update the Case status. Repeat the process for other Cases. This created several operational challenges. 1. Repetitive Manual Work Tracking information had to be checked repeatedly for multiple shipments. 2. Context Switching Agents moved between Dynamics 365 and the FedEx tracking website to complete a single business process. 3. Delayed CRM Updates Even when FedEx had already received a shipment, the corresponding Case could remain unchanged until somebody manually checked it. 4. Human Interpretation FedEx returns multiple tracking events and statuses. Agents had to interpret those events and determine which ones represented meaningful milestones for the organization’s return process. 5. Poor Scalability As the number of return shipments increased, the amount of manual tracking increased with it. The business did not need another screen for agents to monitor. It needed the tracking information to come back to the system where the business process was already being managed: Dynamics 365. Solution Overview I extended the previous FedEx integration by introducing an automated shipment-tracking process. The solution uses: Dynamics 365 Customer Service Dataverse Integration FedEx Tracking API The high-level process is: Dynamics 365 Customer Service | v Active Cases with Tracking Numbers | v FedEx Tracking | v Tracking Response | v Interpret Scan Events | v Determine Shipment Status | v Update Dynamics 365 Case The process runs automatically on a scheduled basis. There is no requirement for a customer service representative to manually visit the FedEx website for every shipment. Functional Integration Approach The functional design was intentionally centered around the existing Case lifecycle. The Case already contained the information required to identify the shipment. The integration therefore did not introduce a separate tracking application or another user interface. Instead, it used the Case itself as the operational source of truth. The process can be summarized as: Scheduled Trigger ↓ Find eligible Cases ↓ Read Tracking Number ↓ Call FedEx Tracking API ↓ Read Tracking Events ↓ Interpret Latest Status ↓ Determine Tendered / Not Tendered ↓ Update Case This approach keeps the integration aligned with the business process rather than creating a separate operational process around the API. Identifying Cases Requiring Tracking … Continue reading Closing the Loop on Return Logistics: How a U.S.-Based Consumer Appliance Manufacturer Automated FedEx Shipment Tracking in Dynamics 365 Customer Service →

Blogger CloudFrontsbloggerEdit Profile Summary Expense management processes in enterprise project environments often require strict documentation controls to ensure financial accuracy and compliance. One common requirement is the mandatory attachment of receipts when submitting expense entries, especially for specific expense categories such as airfare, accommodation, or high-value reimbursements. My blog describes how a project-driven organization streamlined its expense submission workflow using Canvas Apps integrated with Dynamics 365 Project Operations. The solution I had implemented automates the validation and submission process for expense entries while ensuring that receipt files are attached before submission. By combining form validation logic in the Canvas App with backend automation using Power Automate, the organization eliminated the manual process of attaching receipts and creating notes in the system. The result was a seamless, user-friendly expense submission experience that enforces compliance while significantly improving operational efficiency. Table of Contents 1. Customer Scenario 2. Solution Overview 3. Understanding the Expense Data Structure 4. Canvas App Validation Logic 5. Expense Creation and Submission Process 6. Automating Receipt Handling with Power Automate 7. Enforcing Mandatory Receipts for Specific Categories 8. Business Impact 9. Solution Walkthrough 10. Final Thoughts 1. Customer Scenario A Texas based Cyber Security organization managing multiple client engagements relied on Dynamics 365 Project Operations to track project expenses incurred by consultants and field staff. While the system allowed users to create draft expense entries, the process of submitting those expenses required additional manual steps. To submit an expense, users had to: Create the expense entry in draft mode. Upload the supporting receipt manually. Navigate to the expense record. Create an associated Expense Receipt record. Attach the receipt file under Notes (Annotations). Convert the file into the required document format stored in the system. Update the expense status to Submitted. This workflow introduced several challenges: Users frequently forgot to attach receipts. Manual creation of Notes records was error-prone. Finance teams had to follow up for missing documentation. Expense approvals were delayed due to incomplete submissions. Employees found the process unnecessarily complex. The organization needed a simpler, controlled way to ensure receipts were always attached when expenses were submitted, without requiring users to understand the underlying system structure. 2. Solution Overview To address these challenges, a custom expense submission experience was built using Canvas Apps integrated working in conjunction with D365 Project Operations. The solution introduced a dynamic expense entry submission interface where users can: Create expense entries Upload receipt files Submit expenses directly from the app Figure: Canvas App interface enabling dynamic expense entry submission with receipt attachment. Figure: Canvas App interface enabling dynamic expense entry submission with receipt attachment. Behind the scenes, the application automatically: Creates the expense entry in Dataverse Generates the related Expense Receipt record Uploads the receipt file to Notes (Annotations) as a document Updates the expense status to Submitted Figure: A Submitted Expense Entry Record. Figure: The Expense Receipt Record + Receipt PDF Annotation associated with the Expense, without which Submission won’t have been possible. This automation completely overrides the manual procedure of attaching receipts and creating notes, ensuring the process is both compliant and seamless for users. 3. Understanding the Expense Data Structure Within Dynamics 365 Project Operations, expense documentation follows a structured relationship model. The hierarchy looks like this: Expense ↓ Expense Receipt ↓ Notes (Annotation) ↓ Blob/Base64 File Storage of Expense Receipt. Figure: Implementation of the Expense Entry -> Expense Receipt -> Annotation -> Receipt File Workflow. In this structure: The Expense record stores the financial transaction. The Expense Receipt record acts as a container for receipt documentation. The Notes (Annotation) entity stores the actual file. The receipt file is stored as Base64 binary data (blob). While this structure is technically sound, it requires multiple manual steps when performed directly by users. The custom Canvas App abstracts this complexity and handles it automatically. 4. Canvas App Validation Logic To ensure all required data is captured before submission, the Canvas App includes dynamic validation logic. The application checks whether essential fields are populated before allowing the expense to be saved or submitted. These validations include fields such as: Transaction Date Project Expense Category Reimbursable Indicator External Comments Unit Quantity Unit Price If any required field is missing, the user receives an immediate notification explaining what needs to be completed. Example logic used in the application: If( Or( IsBlank(DatePicker2_5.SelectedDate), IsBlank(Project_Combobox_5.Selected), IsBlank(ExpenseCategory_Combobox.Selected), IsBlank(Dropdown1.Selected.Value), IsBlank(External_Input_7.Text), IsBlank(Project_Combobox_6.Selected), IsBlank(NumberInput2.Value), IsBlank(NumberInput2_1.Value) ), Notify(“Required fields are missing.”, NotificationType.Error) ) This validation ensures data completeness before the expense record is created. 5. Expense Creation and Submission Process Once validation passes, the Canvas App uses a Dataverse Patch operation to create or update the expense record. The logic dynamically calculates financial values such as the subtotal based on quantity and unit price. Example logic: Set( varSavedExpense, Patch( Expenses, Defaults(Expenses), { ‘Transaction Date’: DatePicker.SelectedDate, Project: Project_Combobox.Selected, ‘Expense Category’: ExpenseCategory_Combobox.Selected, Quantity: Value(NumberInputQuantity.Value), ‘Unit Price’: Value(NumberInputPrice.Value), Subtotal: Value(NumberInputQuantity.Value) * Value(NumberInputPrice.Value) } ) ); ‘SubmitExpense(CanvasApp)’.Run( varSavedExpense.Expense, First(fileupload.Attachments).Name, First(fileupload.Attachments).Value ); Notify( “Expense submitted successfully.”, NotificationType.Success ) This creates the draft expense entry in the system. 6. Automating Receipt Handling with Power Automate After the expense entry is saved, the Canvas App triggers a Power Automate flow. The flow receives: Expense record ID File name Receipt file content The flow then performs the following steps automatically. Step 1: Create Expense Receipt Record A new Expense Receipt record is created and linked to the expense entry. Step 2: Upload Receipt as Note The receipt file is stored as a Note (Annotation) associated with the expense receipt. This note contains: File Name Document Type Base64 encoded file content MIME type Step 3: Update Expense Status Finally, the expense record status is updated from Draft to Submitted. This ensures the expense becomes available for approval workflows and financial processing. 7. Enforcing Mandatory Receipts for Specific Categories An important requirement D365 PO is ensuring that certain expense categories cannot be submitted without receipts. Examples include: Airline tickets Travel expenses Accommodation High-value reimbursements The Canvas App logic ensures that a receipt file must be attached before submission is triggered. If the … Continue reading Dynamic Expense Entry Submission with Receipt Attachments in Power Apps: A Practical Implementation for a Texas-Based Operational Technology Security Organization →

Summary 1. Built a unified “My Allocations” dashboard in Microsoft Dynamics 365 Project Operations for a project-based professional services organization. 2. Consolidated resource assignments, weekly hour breakdowns, and time entry management into a single custom view. 3. Eliminated the need to navigate between separate Project, Time Entry, and Calendar views for day-to-day tracking. 4. Enabled Practice Managers to switch between team members and instantly review billability without leaving the page. 5. Added inline time entry creation, submission, recall, and deletion all from one interface. 6. Introduced a consolidated calendar view showing all time entries across projects in a single month-at-a-glance layout. 7. Reduced clicks and screen-switching for both individual contributors and managers tracking team billability. Table of Contents Introduction The Business Problem The Solution One Dashboard for Allocations and Time Entries Real-Time Hours Consumption Tracking Inline Time Entry Management The Consolidated Calendar View The Practice Manager View, Billability at a Glance Security and Role-Based Access Business Impact Frequently Asked Questions Conclusion 1. Introduction For teams running project-based delivery on Microsoft Dynamics 365 Project Operations, a simple question, “How many hours are left on this task, and did I log time for it today?”, often takes far more clicks than it should. Resource assignments live in one view, time entries live in another, and consumption summaries require yet another. For project managers tracking billability across an entire team, the problem multiplies with every resource. To solve this, a custom “My Allocations” dashboard was built directly into Dynamics 365 as a web resource, bringing project assignments, weekly hour breakdowns, hours consumption, and time entry management into a single screen. No tab switching, no re-navigation; just one view that adapts to whether you’re an individual contributor or a manager overseeing a team. 2. The Business Problem In a typical Dynamics 365 Project Operations setup, resource assignments, time entries, and consumption reporting exist as separate entities, each with its own view or form. A consultant checking their weekly workload has to open one screen for assignments, another to log time, and a third to check whether they’re over or under budget on a task. For Practice Managers, this friction compounds. Reviewing billability across a team means repeating this multi-screen process for every resource, switching context, re-filtering views, and manually piecing together a picture of who’s on track and who isn’t. The Objective: Build a single, role-aware dashboard where any user can see their assignments, track hours consumed versus planned, and manage time entries; managers can do the same for any resource on the team, without leaving the page. 3. The Solution The “My Allocations” dashboard was designed around one core idea: everything a resource or manager needs for day-to-day tracking should live on one screen. Instead of navigating between the Project entity, the Time Entry list, and separate consumption reports, users get a consolidated view that surfaces assignments, hours, and entry management side by side. The sections below walk through each part of the dashboard and explain how it removes a specific step from the old multi-screen workflow. Figure 1: My Allocations dashboard overview showing summary cards, toolbar, and project hierarchy. 3.1 One Dashboard for Allocations and Time Entries At the top of the dashboard, summary cards provide an instant overview of active projects, active weeks, allocated hours, and assigned tasks. Instead of navigating through multiple Project Operations entities, users immediately understand their workload from a single screen. Each project expands into its assigned weeks, while every week further expands into a detailed day-by-day breakdown of allocated work. This hierarchical layout lets users drill down naturally, from the project level to weekly allocations and finally to individual daily assignments, without leaving the dashboard. By consolidating this information into one interface, the dashboard eliminates repetitive navigation and significantly reduces the time required to understand upcoming work. Figure 2: Project hierarchy showing projects, weekly allocations, and day-level task breakdown. 3.2 Real-Time Hours Consumption Tracking A dedicated Hours Consumption panel gives resources and managers real-time visibility into task progress. For every task, the dashboard displays planned hours, approved hours, submitted hours awaiting approval, remaining hours, and overall consumption using an intuitive progress indicator. Color-coded progress bars immediately communicate project health. Blue indicates healthy consumption, orange highlights tasks approaching their allocated budget, and red clearly identifies tasks that have exceeded planned effort. This removes the need to generate reports or manually compare planned and actual effort across multiple Project Operations views. Figure 3: Hours Consumption panel displaying planned, consumed, submitted, and remaining hours with visual progress indicators. 3.3 Inline Time Entry Management Every task includes built-in actions that allow users to create new time entries or review existing ones without leaving the dashboard. Instead of opening the standard Time Entry entity, users can complete the entire process from the same interface. The entry form captures all required information including work date, duration, role, and external comments. Users may either save entries as drafts or immediately submit them for approval depending on their workflow. Existing entries can also be reviewed, recalled, resubmitted, or deleted directly from the dashboard, significantly reducing navigation while simplifying daily time tracking. Figure 4: Inline Time Entry form used for creating and submitting project hours. Figure 5: Task calendar displaying existing time entries grouped by day and submission status. 3.4 The Consolidated Calendar View Beyond task-specific calendars, the dashboard provides a consolidated monthly calendar that displays every time entry recorded across all assigned projects. Users no longer need to inspect individual tasks separately to understand their monthly workload. Each calendar day displays the total hours logged together with the number of recorded entries. Color indicators provide an instant visual summary of each day’s dominant submission status. Selecting a day immediately displays every recorded time entry beneath the calendar, making monthly reviews significantly faster for both consultants and managers. Figure 6: Consolidated monthly calendar showing all time entries across projects for the selected resource. 3.5 The Practice Manager View – Billability at a Glance For Practice Managers, the dashboard extends beyond personal allocations by introducing … Continue reading Building a Unified My Allocations Dashboard in Microsoft Dynamics 365 Project Operations for an Industrial Cybersecurity Company in Texas →

Summary Designed and deployed a mobile-first Power Apps Canvas App for a Texas-based industrial cybersecurity firm specializing in operational technology (OT) security for oil and gas infrastructure. Unified time tracking, expense management, material consumption logging, and approvals into a single experience integrated with Dynamics 365 Project Operations. Eliminated fragmented desktop-based workflows that delayed project reporting, approvals, and billing. Automated expense receipt processing through Power Automate, improving compliance and reducing manual effort. Implemented project-scoped approval routing to ensure submissions were reviewed only by authorized stakeholders. Enabled real-time project visibility through structured Dataverse-driven workflows and lifecycle tracking. Provided mobile approvals and submission monitoring, dramatically reducing turnaround times. Improved data accuracy, audit readiness, and billing efficiency across field operations. Table of Contents Introduction Requirement & Business Scenario Solution Implementation Implementation Gallery Outcome FAQs Conclusion 1. Introduction Field-driven organizations live and die by the accuracy and speed of their project data. For a company securing critical infrastructure like oil rigs, every hour an engineer spends fighting with a clunky time-entry screen is an hour not spent on the job site — and every delayed expense submission is a delay in client billing and financial reporting. This is the story of how a Texas-based cybersecurity firm moved away from a fragmented, desktop-oriented workflow inside Dynamics 365 Project Operations and adopted a unified, mobile-first Canvas App that brought time tracking, expense submission, and material logging into one place, with built-in compliance controls and project-specific approval routing. The Goal: Build a unified mobile-first experience that allows field engineers to submit time, expenses, and materials from anywhere while ensuring compliance, controlled approvals, and real-time project visibility. 2. Requirement & Business Scenario The firm manages multiple concurrent field engagements using Dynamics 365 Project Operations as its system of record. Consultants and field engineers were expected to log three categories of activity against active projects: Time entries for hours worked Expense entries covering travel, accommodation, airfare, and related costs Material usage logs for equipment, parts, and consumables The core issue was that the underlying system was built for desktop use, not for engineers working on-site at remote rig locations. This created several compounding problems: Field staff had no efficient way to submit entries from a mobile device, so submissions piled up until they were back at a desk. Time, expense, and material tracking lived in separate workflows, forcing users to context-switch between screens for what should have been a single daily task. Expense compliance was inconsistent — receipts were sometimes attached, sometimes forgotten, and the process for linking a receipt to an expense record involved several manual, error-prone steps behind the scenes. Approvals had no project-level boundaries, making it hard to guarantee that only the right project stakeholders could review and approve specific submissions. Project managers lacked real-time visibility into resource usage, which meant billing and client reporting cycles were consistently delayed. Left unaddressed, these gaps were directly affecting data accuracy, audit readiness, and the speed at which the business could invoice clients. 3. Solution CloudFronts designed a unified mobile experience using Power Apps Canvas Apps layered on top of Dynamics 365 Project Operations and Dataverse, built around one guiding principle: One App. All Submissions. Controlled Approvals. Real-Time Visibility. For field users, the app became the single place to submit time entries on a daily or weekly basis, create expense entries with automatic receipt handling, log material consumption against the correct project, and track the live status of every submission. For project approvers, the same app surfaced only the entries tied to projects they were actually responsible for, let them approve or reject submissions directly from their phone, and preserved a clean, audit-ready trail for every decision. Day Mode and Week Mode Users could switch between a detailed single-day entry view, useful for precise logging and corrections, and a bulk weekly view that sped up repetitive data entry — letting each person work the way that suited their role. Calendar-Based Swipe Navigation A Dynamics-style calendar with swipe gestures let users move quickly across days and weeks, reviewing or correcting historical entries without friction. Stage-Aware Interface Every record followed the same lifecycle — Submitted, Pending, Approved, Rejected, Recall Requested, Recall Approved, Recall Rejected — and the UI adapted to whatever stage a record was in. Action buttons such as Submit, Approve, Reject, and Recall only appeared when they were actually valid, significantly reducing user confusion and accidental actions. Conditional Receipt Enforcement Rather than requiring a receipt for every expense category, the app applied compliance rules selectively. Receipts were mandatory for airfare and OT hardware purchases, while remaining optional for lower-risk categories such as meals and local transportation. 4. Implementation The technical implementation centered on a unified Dataverse data model and a set of automations that removed manual work from both the field user and the back office. Unified Data Model Time, expense, and material entries were all structured in Dataverse and linked back to the relevant project, resource, approval record, and — for expenses — supporting documentation. Every submission created a record with a clearly defined lifecycle stage, ensuring all three entry types behaved consistently even though their underlying business logic differed. Validation Before Submission The Canvas App enforced field-level validation before allowing a record to be saved, checking that essentials such as transaction date, project, category, quantity, and cost information were populated. If( Or( IsBlank(DatePicker.SelectedDate), IsBlank(ProjectCombobox.Selected), IsBlank(CategoryCombobox.Selected), IsBlank(QuantityInput.Value), IsBlank(PriceInput.Value) ), Notify(“Required fields are missing.”, NotificationType.Error) ) Patch-Based Record Creation Once validation passed, the application used Dataverse Patch operations to create records and calculate derived values such as expense subtotals dynamically based on quantity and unit price. Automated Receipt Handling For expense submissions, the previously manual chain of creating an Expense Receipt record, attaching a file as a Note, converting it to the correct document format, and updating the status to Submitted was fully automated. The Canvas App passed the expense ID, file name, and file content to a Power Automate flow, which created the Expense Receipt record, stored the file as a Note (Annotation) with the correct MIME type, … Continue reading How an Industrial Cybersecurity Company in Texas Improved Field Time and Expense Tracking with Microsoft Power Apps and Dynamics 365 Project Operations →

Summary Automated end-to-end contract generation, digital signing, and document filing for an Australia-based commercial linen and garments company using Dynamics 365 Sales, Microsoft Power Automate, and Adobe Acrobat Sign. Eliminated manual contract preparation by generating personalized Word contracts directly from accepted Dynamics 365 Quotes using a reusable Word template. Leveraged Adobe Acrobat Sign text tags embedded within the Word template to automatically create signature, date, and fillable fields without manual field placement or custom development. Automated agreement creation, customer notifications, and real-time signing status tracking through Adobe Acrobat Sign, providing complete visibility throughout the contract lifecycle. Implemented a dedicated child Power Automate flow that automatically identified completed agreements from Adobe Sign emails and archived signed contracts into the correct SharePoint document library. Reduced contract turnaround from a manual, multi-step process to a one-click, fully automated workflow while ensuring audit-ready signed documents and eliminating manual document handling. Table of Contents Introduction Business Challenge Procedure End-to-End Flow Why This Approach Works Conclusion Introduction For any business that runs on contracts — service agreements, quotes-turned-orders, vendor sign-offs — the gap between "quote accepted" and "contract signed" is often where deals slow down. Manual document preparation, back-and-forth emails, chasing signatures, and manually filing signed copies all eat into time that should be spent serving the customer. For an Australia based Linen and Garments, a commercial textile services company, CloudFronts built an end-to-end automation that takes a sales quote all the way through to a fully signed, filed contract — with zero manual document handling in between. The solution combines a Word contract template, Microsoft Power Automate, and Adobe Acrobat Sign, orchestrated across two connected flows: a parent flow that creates and sends the contract, and a child flow that listens for the signed response and files it automatically. This post walks through how that solution works, including the one detail that makes the whole thing possible without any custom code: Adobe Sign text tags embedded directly inside the Word template. The Business Challenge Once a quote is accepted, the team needed the resulting contract to: Be generated automatically from the quote and its line items — no manual copy-pasting of customer details into a Word document. Be sent for signature immediately, with the right fields ready for the customer to fill in and sign — bank details, account information, and a signature block, all in the right place. Notify both the customer and the internal Adobe Sign account holder the moment it’s out for signing. Automatically file the final, fully signed PDF back into the correct SharePoint location tied to that quote — without anyone needing to remember to save it. Doing this by hand across multiple people and mailboxes was slow and error-prone. The goal was to make the entire journey — quote to signed, filed contract — happen in minutes, with no manual document work at any step. Procedure Step 1: Auto-Generating the Contract from the Quote The process starts with a single action: Create Contract. This triggers the parent Power Automate flow, which: Composes the Quote ID from the selected record. Retrieves the document location tied to that quote (the Word contract template). Pulls the Quote, the associated Customer, and the Contact record for the signer. Uses these to populate a Word template — the standard “Populate a Word Template” merge step — filling in customer name, contract terms, line items, and contact details automatically. This is the same idea used in most contract-automation flows: merge structured CRM/quote data into a pre-built Word template, so the resulting document is fully personalized without a single manual edit. Step 2: Making the Contract Signable — Text Tags in the Template This is the step that makes the entire signing experience work, and it's worth explaining properly, because it's easy to get wrong. A merged Word document, by itself, is just static text. For Adobe Acrobat Sign to know where a customer needs to sign, initial, or fill something in, the template needs special markers called text tags — plain text strings embedded directly into the Word template before it's ever merged. When the finished document is sent to Adobe Sign, Adobe automatically scans it, finds these tags, and converts them into live, interactive fields for the signer. For the contract, the template includes tags like: {{Customer_Sign_es_:signer1:signature}} {{Date_Of_Signature_es_:signer1:date}} {{Financial_Institution_es_:signer1}} {{BSB_Number_es_:signer1}} {{Account_Name_es_:signer1}} {{Account_Number_es_:signer1}} Each tag follows Adobe's syntax: a field name, the _es_ identifier, the signer role (signer1), and an optional field type (signature, date, or left blank for a plain fillable text box). Because these tags are just text, they can sit anywhere in the Word template exactly where the business wants the field to appear — no separate field-placement tool required. Getting this right matters more than it looks. A few lessons learned building this out: The entire tag must stay on a single line and in a common font — if it wraps across a line break during merge or PDF conversion, Adobe won’t recognize it, and the raw tag text stays visible instead of becoming a field. Field type directives are limited to what Adobe actually supports (signature, date, initials, etc.) — leaving the type off entirely creates a plain fillable text field, which is what was used for the banking detail fields here. Converting the merged Word document to PDF before sending it to Adobe Sign tends to produce more consistent tag detection than sending the raw .docx. Because the tags are static text baked into the template, no extra configuration is needed in Power Automate to "activate" detection — it happens automatically the moment the document is sent to Adobe Sign for signature. Step 3: Sending the Contract for Signature Once the Word template is fully populated, the flow hands it off to Adobe Acrobat Sign using the Create an agreement from a file content and send for signature action — passing the merged file straight through, along with the signer's name, email, and role. At this point, two things happen simultaneously: a) The customer's Contact person receives … Continue reading From Quote to Signed Contract in Minutes: Automating Adobe Acrobat Sign Integration for an Australia based Linen and Garments company →

Are You Struggling to Understand Where Your Customer Cases Stand? As appliance brands grow, managing customer service requests becomes increasingly complex. Warranty claims, replacement requests, product issues, and customer inquiries can quickly overwhelm teams if there isn’t a structured process in place. Have you ever found yourself asking: “Where is this case right now?“ It sounds like a simple question, yet in many organizations, finding the answer requires checking multiple systems, following up with different teams, or waiting for updates from customer service representatives. The issue isn’t a lack of effort; it’s a lack of visibility. Most customer service systems rely on a handful of generic case statuses such as Open, In Progress, or Closed. While these statuses indicate whether a case is active, they reveal very little about what is actually happening behind the scenes. For appliance manufacturers, a customer service case often involves much more than a support ticket. Warranty validation, product registration checks, troubleshooting, replacement approvals, shipping coordination, and customer follow-ups all form part of the resolution journey. This is where Multi-Stage Business Process Flows (BPFs) in Microsoft Dynamics 365 can make a significant difference. Why Traditional Case Management Falls Short Imagine a customer contacts support because their toaster is no longer heating properly. A standard ticketing process may record the issue and mark the case as “In Progress.” A single status value cannot answer these questions. As a result, service teams spend time chasing updates, managers struggle to identify bottlenecks, and leadership lacks visibility into where cases are getting delayed. Example: Imagine two cases both marked as “In Progress.” From a traditional status perspective, both cases appear identical. With a Multi-Stage BPF, the difference becomes immediately visible, enabling managers to prioritize actions and allocate resources more effectively. A Better Approach: Multi-Stage Business Process Flows A Business Process Flow (BPF) in Dynamics 365 provides a guided framework that moves a case through predefined stages. Each stage can contain mandatory fields, validations, and business rules, ensuring that critical information is captured before the case progresses further. Rather than relying on a single status value, organizations gain visibility into exactly where a case sits within the overall service journey. For a premium appliance manufacturer, a typical service case might progress through the following stages: Bringing Structure to the Appliance Service Journey A Multi-Stage Business Process Flow transforms a case from a simple ticket into a clearly defined process. Instead of tracking a case using one status field, the case progresses through a series of business stages that mirror the real-world workflow. For example, a warranty replacement case for a defective toaster may move through stages such as: 1. ID & Research – Customer Information The service team captures and validates customer information, product registration details, serial number, purchase source, warranty eligibility At this stage, the goal is to verify that the claim is legitimate and gather all required information. 2. Receiving The returned product is reviewed and inspected. Teams can confirm receipt of the item, validate the reported issue, document inspection findings This ensures that decisions are based on actual product conditions rather than assumptions. 3. Accounting Before a replacement is issued, financial and operational reviews may be required. Activities can include warranty claim validation, credit approvals, replacement authorization, internal accounting reviews This creates accountability while maintaining process consistency. 4. Shipping Once approved, the replacement process moves into fulfillment. Required information may include tracking number, shipping date, return label status, logistics confirmation At this stage, the customer is actively waiting for their replacement product. 5. Resolve Case Once delivery is confirmed and the customer is satisfied, the case can be formally closed. The entire service journey is documented from start to finish. A Real-World Customer Story Imagine Sarah purchased a toaster a few months ago and suddenly found that it stopped heating. She contacts customer support expecting a quick resolution. Behind the scenes, her request needs to pass through product verification, warranty validation, inspections, approvals, and shipping before a replacement reaches her doorstep. Without a structured process, delays can occur at any stage, leaving both the customer and support teams frustrated. With a Multi-Stage BPF, every step is visible, tracked, and managed, ensuring the case continues moving forward while providing clarity to both employees and customers. Why This Matters for Leadership The biggest benefit of Multi-Stage BPFs is not just process control—it’s visibility. When cases are tracked by stage, leaders can quickly identify where delays are occurring. For example: Instead of simply knowing that cases are open, leaders gain insight into why they are still open. This makes it easier to make informed decisions and address bottlenecks before they impact customer satisfaction. Why We Believe in Structured Service Management At CloudFronts, we’ve worked with organizations looking to streamline customer service operations using Dynamics 365. One common challenge we consistently encounter is the lack of visibility into the lifecycle of customer requests. Through our implementations and observations, we’ve found that Multi-Stage Business Process Flows help organizations bring structure, accountability, and transparency to service operations while improving the overall customer experience. More importantly, they help leadership teams move from reactive case management to proactive service management. Better Accountability Across Teams Customer service cases often involve multiple departments. Without a structured process, it’s easy for tasks to fall through the cracks during handoffs. A Multi-Stage BPF helps ensure that each team completes its responsibilities before the case moves forward. Required information can be captured at each stage, creating consistency across the organization while also improving data quality. Most importantly, everyone involved knows exactly what needs to happen next. Improving the Customer Experience Customers don’t care which internal department owns the next step. They simply want their issue resolved quickly and efficiently. By providing a clear, structured process, organizations can reduce delays, improve communication, and deliver a more consistent customer experience. For appliance brands, where warranty claims and replacement requests can directly influence customer loyalty, these improvements can have a significant impact. Final Thoughts A customer service case is rarely just a ticket. Behind every … Continue reading Managing Complex Warranty and Replacement Requests with Dynamics 365 Multi-Stage Business Process Flows for a North American Appliance Brand →

Sustainability certification is one of the most operationally demanding programs a nonprofit can run. It is not just a badge on a product, it is a multi-year, multi-stakeholder process involving manufacturers, independent assessment bodies, scoring frameworks, document issuance, and public transparency requirements. When you are managing thousands of products across global industries, the cracks in a manual, spreadsheet-driven operation show up fast. This is exactly the situation a Netherlands-based nonprofit found itself in. The organization administers a globally recognized product sustainability certification program, assessing products across five dimensions: material health, product circularity, clean air and climate protection, water and soil stewardship, and social fairness. Products move through certification levels Bronze, Silver, Gold, and Platinum across a lifecycle that spans application, third-party assessment, issuance, and periodic recertification every three years. As certification volumes grew, so did the operational complexity. Disconnected tools, manual document preparation, and no single place to track everything meant the team was spending more time managing the process than running it. Rather than bolt on yet another external tool, the organization made a deliberate architectural choice: build the entire certification management platform inside Microsoft Dynamics 365, extend it with Azure Function Apps for automation, and expose public APIs for ecosystem transparency. The Goal Build a unified, scalable certification lifecycle management system inside Dynamics 365 that automates document generation, manages logo assets, and exposes public APIs for published certification data — all without introducing new platform dependencies. The Business Problem To understand what was built, you first need to understand what was broken. The organization’s operational teams were trying to answer some fairly fundamental questions every single day — What is the current certification status of a given product? Which products are approaching their recertification deadline? Which assessment body certified a product and when? Is the certificate document ready for issuance? None of these questions had a reliable, centralized answer. Certification records lived across disconnected spreadsheets and email threads, which meant any “current” view of a product’s status was only as accurate as the last person who updated a row. Certificate documents were manually composed for every issuance a slow, error-prone process that created formatting inconsistencies and delayed the experience for certified manufacturers. Logo assets were managed informally, with no version control or consistent delivery process. No Single Source of Truth Certification records scattered across spreadsheets and email threads with no reliable current view. Manual Document Creation Every certificate composed by hand slow, inconsistent, and a bottleneck manufacturers felt directly. Zero Public Transparency External stakeholders relied on manually updated static pages with no programmatic access to live data. Unscalable Operations Growing program volumes with no automation meant every new product added to the manual workload. The Solution Architecture The platform was designed around one principle: build close to where the operational data already lives, and automate at the right trigger points rather than everywhere at once. The solution runs on three deliberate layers. Critically, this architecture avoided over-engineering entirely — no separate data warehouse, no heavy ETL pipeline, no dedicated certification SaaS platform requiring its own licensing and maintenance. Everything runs inside the Microsoft ecosystem. 1 Data Layer — Custom Dynamics 365 Tables Purpose-built Dataverse tables that mirror the certification domain exactly, products, certification events, assessment bodies, category scores, and logo assets all in a single relational, auditable structure. 2 Automation Layer — Azure Function Apps, Dynamics Plugins Two event-driven Function Apps sit alongside the CRM one for certificate document generation, one for logo package delivery, both triggered by real state changes in the certification lifecycle, not a schedule. 3 Transparency Layer — Public REST APIs Public-facing APIs expose published certification data to external stakeholders, brands, retailers, regulators, and third-party platforms without any manual data exchange with the organization. Custom Dynamics 365 Data Model The data model is the foundation everything else rests on. Rather than forcing certification concepts into standard CRM entities that were never designed for this domain, the team built purpose-specific custom tables inside Dataverse that mirror how the certification program actually works. Product data Core product records, variants, and identifiers — the foundational layer that everything else references. Application handling Applications, assessments, category and requirements assessments — all managed within accounts. Assessment bodies and related workflows live here too. Public-facing entities Public tables for products, certifications, certificates, and product variants — the data layer that powers external visibility and API exposure. Together, these layers gave the organisation a complete, relational view of every certified product across its full lifecycle — all within a single operational platform. Certificate Document Generation via Azure Function App Before this system existed, every certificate document was created by hand. Someone would take a template, fill in the product details, format it, check it, and send it. For an organization issuing certificates across thousands of products, this was not just slow — it was a source of constant inconsistency and a bottleneck that manufacturers felt directly. The Azure Function App for certificate generation eliminated this entirely. Here is how it works end to end: How It Works ⚡ Trigger Certification record reaches the correct status in Dynamics 365 → 🔍 Fetch Pulls record + product data via Dynamics 365 Web API → 📄 Generate Selects correct template, populates all fields, generates document → 🔗 Store & Link Saves document and links it back to the certification record What this means in practice is that certificate issuance is now consistent, fast, and entirely hands-off for the operational team. Formatting is guaranteed every time because the template logic is defined once and applied uniformly. The function also runs independently of the CRM interface — making it resilient and reusable across multiple trigger scenarios, including bulk recertification processing. The impact: A task that previously required manual effort for every single issuance now requires none. Eliminated entirely. Logo Image Generation via Azure Function App A certified product comes with more than a document — it comes with the right to use the certification mark. For manufacturers, that logo is a commercial asset. It goes … Continue reading How a Netherlands-Based Non-Profit Transformed Certification Management with Dynamics 365 and Azure Functions →