No Plugin, No Flow: Auto-Propagating Legal Entity Across 18 D365 Tables Using Formula Fields Summary As part of our internal PO (Project Operations) to F&O integration product, every transaction needs to know which legal entity it belongs to — yet no out-of-box mechanism exists to propagate this across the 18+ connected tables involved. We built a zero-code, zero-maintenance solution using Dataverse formula fields: set Legal Entity once on Account, and every related record inherits it automatically. A custom Legal Entity table maps company master records to FO DataAreaId codes, and formula fields chain the value down through the entire relationship hierarchy. Three entities with polymorphic lookups blocked formula traversal — solved with a direct lookup field auto-populated via a Business Rule, requiring no user action. Business impact: eliminated manual per-record entry, removed CRM–FO mismatch risk, and replaced plugin/flow maintenance overhead with pure declarative formula fields. Table of Contents 01 Summary 02 The Challenge 03 What We Built 04 How It Works 05 The One Technical Wall 06 The Outcome 07 The Bigger Point 08 FAQs 09 Conclusion 10 About Me The Challenge In our internal PO (Project Operations) to F&O integration product, every transaction needs to know which legal entity it belongs to — yet no out-of-box mechanism exists to auto-propagate this across the 18+ connected tables involved. The traditional approach? Manual entry, plugins, or complex flows — all high maintenance, all error-prone. What We Built A zero-code, zero-maintenance auto-propagation solution using Dataverse formula fields — no plugin, no Power Automate flow for downstream entities. The core idea: set Legal Entity once on Account. Every related record inherits it automatically. How It Works One custom table — Legal Entity — stores company master records mapped to FO DataAreaId codes (e.g. ac, USMF). One manual input — user sets Legal Entity on Account. That’s it. Everything else is automatic — formula fields chain through the relationship hierarchy. Account (set once) → Contact, Project Contract, Invoice → Contract Lines, Projects → Tasks, Time Entries, Expenses, Actuals, Team Members, Role Prices… The One Technical Wall Three entities — Contact, Salesorders, Invoices, Projects — use polymorphic lookup fields that block formula traversal. Solved by adding a clean direct lookup — cf_accountref — populated automatically via a Business Rule. No user action needed. The Outcome Before After Legal Entity entered manually per record Set once on Account — cascades to 18 tables Risk of mismatch between CRM and FO Single source of truth — always in sync Plugin or flow required for automation Pure formula fields — zero maintenance Existing records needed manual update One-time bulk flow backfilled all records The Bigger Point Data Governance Principle This isn’t just a technical pattern — it’s a data governance principle: in multi-entity implementations, master attributes should live at the top of the hierarchy and flow down automatically, not be re-entered at every level. Formula fields make this possible in Dataverse without a single line of code. Frequently Asked Questions Why not just use a plugin or Power Automate flow instead? Plugins and flows both introduce ongoing maintenance overhead — deployment, error handling, throttling limits, and monitoring. Formula fields are declarative, run natively inside Dataverse, and require no execution infrastructure or upkeep. What happens when a polymorphic lookup blocks the formula chain? Dataverse formula fields can’t traverse polymorphic (multi-target) lookups directly. The fix is a dedicated single-target lookup field, populated automatically by a Business Rule, that formula fields can then reference downstream. Does this approach scale beyond 18 tables? Yes. As long as each new table has a traceable relationship path back to Account (directly or through an intermediate entity), a formula field can be added to inherit Legal Entity without any additional plugin or flow logic. What about records that already existed before this was implemented? A one-time bulk update was run to backfill Legal Entity on existing records. Going forward, all new and related records inherit the value automatically through the formula field chain. Conclusion Legal Entity tracking is a small field with outsized consequences — get it wrong, and financial reporting, cross-entity reconciliation, and downstream automation all inherit the error. The instinct in most implementations is to reach for a plugin or a flow to keep it in sync. This solution proves that’s not always necessary. By anchoring Legal Entity at the top of the hierarchy on Account and letting Dataverse formula fields carry it down through 18 connected tables, we removed an entire category of maintenance — no custom code to patch, no flow runs to monitor, no throttling limits to worry about. The system simply stays correct by design. It’s a reminder that the most resilient integrations are often the ones that need the least ongoing attention. When a platform-native feature can solve a problem cleanly, it usually outlasts a custom-built one. About Me DC Author Deepak Chauhan Consultant and Databricks Certified Data Engineer with 4 years of experience across Dynamics 365, Data & AI, and BI. Building Something Similar? If you’re wrestling with multi-entity data consistency in Dataverse or D365, formula fields might solve more than you expect — before you reach for a plugin or a flow. Get in Touch

How Project-Based Profitability Reporting Turns Dynamics 365 PSA Data into Business Decisions Summary Managing multiple customer engagements means thousands of monthly records — time entries, resource allocations, invoices, and project costs — yet this data often remains fragmented across systems, making it difficult to answer one critical question: “Is this project actually profitable?” We built a comprehensive profitability reporting solution using Dynamics 365 PSA and Power BI for a Microsoft Solutions Partner headquartered in Texas, USA, delivering enterprise technology services across multiple practice areas. The solution unifies financial and operational data into two complementary dashboards: an Executive Profitability Overview for leadership and a Detailed Hours & Financial Analysis page for project managers. Key capabilities include continuous gross margin monitoring, resource utilization tracking linked directly to profitability, solution-area performance analysis, and dynamic filtering by project, manager, status, and date. Business impact: manual financial reconciliation was replaced with automated real-time dashboards — enabling earlier margin interventions, reduced revenue leakage, and faster executive decision-making. Table of Contents 01 Summary 02 About the Customer 03 The Challenge 04 The Solution 05 Executive Dashboard 06 Profitability Trends 07 Resource Utilization 08 Business Impact 09 FAQs 10 Conclusion About the Customer Customer Spotlight A Microsoft Solutions Partner — Texas, USA Our customer is a leading Microsoft solutions provider headquartered in Texas, USA, delivering enterprise solutions across cybersecurity, cloud infrastructure, systems management, mobility, and business intelligence. With numerous customer projects running simultaneously, leadership required a centralized reporting solution to monitor project financial health across the organization. The Challenge Most organizations using Dynamics 365 PSA successfully capture operational data. The problem isn’t collecting it — the problem is connecting it into meaningful business insights. Project managers frequently found themselves asking: 1Which engagements are generating healthy margins? 2Which projects are consuming more cost than expected? 3How much revenue has actually been billed? 4Are allocated resources being utilized efficiently? 5Which solution areas contribute the highest profitability? Answering these questions required manually comparing multiple reports across finance, operations, and project management. By the time profitability issues were discovered, corrective action was often too late. The Solution To eliminate fragmented reporting, we designed a centralized Engagement Profitability Report in Power BI using Dynamics 365 PSA as the primary data source. The report is divided into two complementary dashboards: Executive Profitability Overview Strategic visibility with consolidated KPIs, margin trends, and interactive portfolio filters for leadership teams. Detailed Hours & Financial Analysis Operational drill-down to engagement and resource level, enabling project managers to trace profitability directly. Dynamics 365 PSA Integration Primary data source connecting contracts, actuals, time entries, invoices, and resource allocations in one model. Power BI Analytics Layer Dynamic filtering, trend analysis, treemap solution-area breakdowns, and real-time gross margin monitoring. Executive Profitability Dashboard The executive dashboard provides leadership with an instant view of project performance. It consolidates key KPIs into one interactive page: Total Contract Value Original Contract Amount Change Orders & Value Total Cost Incurred Gross Margin Amount Gross Margin % Billable Hours Non-Billable Hours Invoice Amount The dashboard also includes interactive filters for Project Status, Project, Project Manager, and Date Range — enabling instant analysis across any project portfolio without rebuilding reports. Profitability Trends Over Time One of the most valuable capabilities is tracking profitability throughout the project lifecycle rather than waiting until project closure. Management can continuously monitor: Monthly cost incurred vs. monthly billable revenue Invoice trends and billing progress Gross margin performance over time These trend analyses quickly surface rising project costs, revenue slowdowns, billing delays, and margin deterioration — transforming profitability reporting from a historical exercise into an operational management tool. “A project may have a high contract value but low billable utilization, delayed invoicing, and increasing delivery costs — the report surfaces this gap immediately.” Resource Utilization Insights People are the largest investment in professional services organizations. The report compares Allocated Hours, Billable Hours, and Non-Billable Hours at both project and individual resource levels, helping managers identify: Under-utilized consultants Excessive non-billable work patterns Resource allocation imbalances across engagements Delivery efficiency trends by team member Instead of tracking utilization in isolation, the report links it directly to project profitability through resource-level cost breakdowns showing Role, Allocated Hours, Billable Revenue, and Delivery Cost per person. Solution Area Performance Using Power BI treemap visualizations, the report analyzes profitability across Solution Areas, Solution Plays, and Business Units — enabling strategic questions such as: Which service offerings generate the highest margins? Which solution areas consume the highest delivery cost? Where should future investment be focused? Business Impact Before After Multiple disconnected operational reports Unified profitability dashboard Manual financial reconciliation Automated real-time reporting Limited visibility into project margins Continuous gross margin monitoring Separate operational and financial analysis Single integrated business view Difficult executive reporting Interactive executive dashboards Resource utilization tracked independently Utilization linked directly to profitability Frequently Asked Questions Does Dynamics 365 PSA provide profitability reporting out of the box? Dynamics 365 PSA captures the underlying operational data, but organizations typically require customized Power BI reports to combine contracts, costs, invoices, resources, and profitability metrics into meaningful business insights. Why combine operational and financial data in one report? Project profitability depends on multiple factors including hours worked, delivery cost, billing progress, and contract value. Bringing these together provides a complete view of project health and supports faster, more informed decisions. Who benefits most from this type of report? Executive leadership, project managers, finance teams, PMOs, and delivery managers all benefit. Executives gain portfolio-level visibility, while project managers can investigate profitability at the engagement and resource levels. Can this be extended to other Dynamics 365 modules? Yes. The same Power BI model can be extended to incorporate data from Dynamics 365 Finance & Operations, including actuals from Project Accounting, enabling even deeper financial reconciliation across modules. Conclusion Project success is measured by more than completed tasks or delivered hours — it is ultimately defined by profitability. By bringing together Dynamics 365 PSA operational data and Power BI analytics, organizations gain a real-time view of project financial performance. Instead of asking “Was the project … Continue reading How Project-Based Profitability Reporting Turns Dynamics 365 PSA Data into Better Business Decisions →

Summary A Computer Security Service provider based in Houston, Texas needed a better way to review large-scale project reports where financial, billing, delivery, and schedule metrics were difficult to analyze in a flat table structure. This blog explains how a Power BI Matrix visual was used to create grouped business headers such as: Contract & Billing Status Schedule Status Budget & Hours Cost Performance & Forecast The solution uses: Custom DAX mapping tables Dynamic SWITCH measures Matrix column hierarchies Custom sorting logic The final report improved readability and made project reviews easier by grouping related KPIs into meaningful business sections for leadership and delivery teams. Power BI Matrix visual with grouped business headers Table of Contents 1. The Reporting Problem 2. Why Matrix Visual Was Used 3. Create a Header Mapping Table 4. Create the Dynamic Measure 5. Configure the Matrix Visual 6. Important Limitations and Learnings 7. Frequently Asked Questions 8. Conclusion The Reporting Problem A company working in industrial infrastructure and operational technology services needed a better way to review project financial and delivery data inside Power BI. The existing report already contained all required metrics, including: Contract value Budget usage Project schedule Billing status Margin calculations Cost forecasts Although all required information existed in the report, the layout was difficult to review because every column appeared as a flat list. During project review meetings, users had to manually scan unrelated columns to understand project health. The business requested: Grouped business sections Better column organization Formula explanations for KPIs Easier financial review Structured project reporting The goal was to organize the report in the same way projects are discussed during operational reviews. Why Matrix Visual Was Used Power BI table visuals do not support grouped or merged headers. To create multi-level business headers, the report had to use a Matrix visual. This allowed related columns to appear under parent business sections such as: Contract & Billing Status Schedule Status Budget & Hours Cost Performance & Forecast This structure made the report easier to scan during financial and project discussions. Create a Header Mapping Table The first step was creating a metadata table that controls: Group names Column names Column order Section order This table drives the Matrix visual structure dynamically. DAX Table Project Matrix Headers = DATATABLE( “Group Name ➡️”, STRING, “Column Header”, STRING, “Sort”, INTEGER, “Master_Sort”, INTEGER, { {“Project Identification”, “Billing Method”, 1, 1}, {“Overall Project Status”, “Overall Project Status”, 5, 2}, {“Contract & Billing Status”, “Contract Total (FF)”, 6, 3}, {“Contract & Billing Status”, “Contract Not-to-Exceed (T&M)”, 7, 3}, {“Contract & Billing Status”, “Payment Terms”, 8, 3}, {“Contract & Billing Status”, “YTD Invoiced Amount”, 9, 3}, {“Contract & Billing Status”, “% Invoiced”, 10, 3} } ) After creating the table: Column Header was sorted by Sort Group Name ➡️ was sorted by Master_Sort Without this step, Power BI sorts headers alphabetically, which breaks the business layout. Create the Dynamic Measure The Matrix visual uses one dynamic measure that returns values based on the selected column header. This was implemented using SWITCH(). Dynamic Measure Project Matrix Values = SWITCH( SELECTEDVALUE(‘Project Matrix Headers'[Column Header]), “Billing Method”, MAX(salesorder[Billing Method]), “Overall Project Status”, MAX(msdyn_projects[Overall Project Status]), “Contract Total (FF)”, SUM(salesorder[Total Amount]), “Contract Not-to-Exceed (T&M)”, SUM(salesorder[Not-to-exceed Limit]), “Payment Terms”, MAX(salesorder[Payment Terms]), “YTD Invoiced Amount”, SUM(invoice[Total Amount]), “% Invoiced”, invoice[% Invoiced] * 100 ) Aggregation handling became very important during implementation. Metric Type Correct Aggregation Amounts SUM Status MAX Dates MAX or MIN Percentages AVERAGE or calculated measure Using incorrect aggregation inside the SWITCH measure can produce duplicate totals, incorrect percentages, or unexpected values. Configure the Matrix Visual The Matrix visual was configured using: Matrix Area Field Rows Business Unit → Client → Project Name Columns Group Name ➡️ → Column Header Values Project Matrix Values This automatically created grouped business headers. Power BI Matrix visual configured with grouped business headers Important Limitations and Learnings Grouped Headers Only Work Properly for Columns Power BI supports grouped headers only through the Columns section of the Matrix visual. Dynamic grouping for Matrix row headers is limited. For example: Business Unit Client Project Name cannot be dynamically grouped the same way as column headers. Since these row sections were static, text boxes and manual formatting were used to simulate grouped row labels. Aggregation Logic Must Be Handled Carefully The dynamic measure requires every metric to be properly summarized and mapped. Incorrect aggregation logic can produce: Incorrect totals Duplicate values Wrong percentages Blank results This becomes especially important in financial and project reporting where different KPIs require different summarization methods. Matrix Visual Performance Large Matrix visuals with many dynamic measures can become slow. Performance was improved by: Reducing unnecessary measures Avoiding repeated calculations Using summarized tables Keeping hierarchies simple Frequently Asked Questions Can Power BI tables create grouped headers? No. Standard table visuals do not support grouped or merged headers. The Matrix visual is required for this approach. Why use a Matrix visual instead of a Table visual? Matrix visuals support hierarchical columns, allowing related KPIs to appear under common business headers. Does Power BI support dynamic row grouping? No. Dynamic grouping for row headers is limited. Static row sections usually require text boxes and manual formatting. Why do Matrix values sometimes show incorrect totals? This usually happens because aggregation logic inside the SWITCH measure is incorrect. Each KPI must use the proper summarization method such as: SUM MAX MIN AVERAGE Dedicated calculated measures Conclusion Power BI Matrix visuals can be used to create structured multi-level business headers for large operational reports. By combining: Matrix hierarchies DAX metadata tables Dynamic SWITCH measures Custom sorting logic large reports can be organized into meaningful business sections that are easier to review and maintain. The most important learning from this implementation was understanding the limitations of Matrix visuals and handling aggregation logic carefully. When implemented correctly, this approach makes project and financial reporting significantly easier for leadership teams to use. We hope you found this blog useful. If you would like to discuss similar Power BI visualization solutions, … Continue reading From Unstructured Project Data to Executive-Ready Reporting: Transforming Project Reviews with Power BI Matrix Visuals for a Houston-Based Industrial Cybersecurity Provider. →

Summary We implemented an automated cost control process for our internal AI Sales Insights solution running in Azure. Azure Budget Alerts were connected with Automation Runbooks to automatically stop resources once spending crossed a defined threshold. The setup reduced manual monitoring and helped us maintain tighter control over Azure consumption. The solution used native Azure services with Managed Identity authentication for secure automation. The same approach can be extended to Azure Virtual Machines, App Services, Databases, and other Azure resources. Azure Budget Alerts integrated with Automation Runbooks for automated cost control Table of Contents 1. Why We Needed This 2. Solution Overview 3. Azure Services Used 4. Step 1: Create the Azure Budget 5. Step 2: Create an Action Group 6. Step 3: Create the Automation Runbook 7. Step 4: Enable Managed Identity 8. Step 5: Assign Required Permissions 9. Step 6: Test the Complete Flow 10. Business Impact 11. Frequently Asked Questions 12. Conclusion Why We Needed This Our AI Sales Insights solution uses Azure services such as Function Apps and AI processing components to generate and process sales insights. Since the environment runs on a Pay As You Go subscription, costs can increase unexpectedly if resources continue running after active usage hours or during extended testing cycles. Initially, we were monitoring costs manually through Azure Cost Management dashboards and email alerts. However, this approach had a few limitations: Alerts were sometimes noticed too late Resources continued running even after thresholds were reached Development environments stayed active longer than needed Manual intervention was required every time We wanted a simple solution where Azure could automatically take action when spending crossed a defined limit. Solution Overview We implemented the following workflow: Azure Budget continuously monitors subscription spending A Budget Alert gets triggered when the threshold is reached The alert calls an Azure Action Group The Action Group triggers an Automation Runbook The Runbook authenticates using Managed Identity The Runbook automatically stops the Azure resource This gave us a lightweight and reliable automation setup for controlling costs. Azure Services Used Service Purpose Azure Cost Management Monitor Azure spending Azure Budget Alerts Detect threshold breaches Azure Action Groups Trigger automation Azure Automation Execute PowerShell Runbooks Managed Identity Secure authentication Step 1: Create the Azure Budget We started by creating a budget inside Azure Cost Management. Azure Budget configuration for automated cost monitoring Budget Configuration Setting Value Budget Amount ₹800 INR Reset Frequency Monthly Forecast Alert 90% Actual Cost Alert 100% One important thing we learned during implementation is that Azure budget calculations are not always real time. If automation starts only at 100%, additional usage may already occur before the alert executes. Because of this, setting automation thresholds slightly earlier, usually around 85% to 90%, is safer for production environments. Step 2: Create an Action Group Next, we created an Azure Action Group. The Action Group acts as the bridge between the Budget Alert and the Automation Runbook. Set Action Type as Automation Runbook Select the Automation Account Link the target Runbook Once configured, Azure automatically executes the Runbook whenever the budget alert is triggered. Step 3: Create the Automation Runbook Inside Azure Automation, we created a PowerShell Runbook using Runtime Version 5.1. The Runbook dynamically accepts Azure resource values instead of hardcoded names, making it reusable across multiple environments. Dynamic PowerShell Script # Variables $ResourceGroupName = “{Your Azure Resource Group Name}” $FunctionAppName = “{Your Azure Function App Name}” # Authenticate using System Managed Identity try { Connect-AzAccount -Identity Write-Output “Successfully authenticated with Managed Identity” } catch { Write-Error “Failed to authenticate: $_” exit 1 } # Stop Azure Function App try { Stop-AzFunctionApp ` -Name $FunctionAppName ` -ResourceGroupName $ResourceGroupName ` -Force Write-Output “Function App stopped successfully” } catch { Write-Error “Failed to stop Function App: $_” exit 1 } Step 4: Enable Managed Identity To avoid storing credentials inside the script, we enabled System Assigned Managed Identity for the Automation Account. This allowed the Runbook to authenticate securely against Azure without usernames, passwords, or secrets. This approach is cleaner, more secure, and easier to maintain. Step 5: Assign Required Permissions After enabling Managed Identity, we assigned RBAC permissions to the Automation Account on the target resource. The following roles were used: Contributor Website Contributor Function App Contributor Without proper permissions, the Runbook may authenticate successfully but still fail while stopping resources. Step 6: Test the Complete Flow Before connecting everything to the Budget Alert, we tested the Runbook manually. Verify Managed Identity authentication Confirm the Azure resource stops correctly Validate RBAC permissions Test Action Group execution Once everything worked successfully, the Runbook was connected to the Budget Alert. Business Impact Area Before After Cost Monitoring Manual Automated Resource Shutdown Manual Automatic Response Handling Manual Action Required Automatic Resource Shutdown Cost Governance Reactive Proactive This setup helped us reduce unnecessary runtime costs and eliminated the need for continuous manual monitoring of our AI Sales Insights environment. Conclusion This implementation helped us build a simple and practical cost governance process for our internal AI Sales Insights solution. Instead of relying only on dashboards and email notifications, Azure now takes automated action whenever spending crosses the configured threshold. As AI workloads continue growing, automating cloud cost control will become increasingly important for maintaining predictable and manageable Azure spending. We hope you found this blog useful. If you would like to discuss similar Azure automation and cost optimization solutions, feel free to connect with us at transform@cloudfronts.com .

Summary A services firm based in Houston, Texas, specializing in enterprise security solutions, improved operational efficiency by transitioning from Excel-based reporting to Power BI Paginated Reports, implemented by CloudFronts. CloudFronts designed a structured, client-ready reporting solution integrated with Dynamics 365 CRM. The solution supports manual distribution today while being fully prepared for future automation such as scheduled PDF delivery. Business impact: Improved operational efficiency, standardized reporting, and scalability without rework. Client-ready account statement using Power BI Paginated Reports About the Customer As a 9x Microsoft Gold Partner and 6x Microsoft Advanced Specialization-endorsed organization based in Texas, U.S., the customer specializes in delivering solutions for critical business needs across systems management, security, data insights, and mobility. The Challenge Initially, the organization generated account statements manually using Excel for a small number of clients. While this approach worked at a smaller scale, it presented several limitations: Manual effort and inefficiency: Reports had to be created individually for each client. Lack of standardization: Formatting and structure varied across reports. Scalability concerns: While effective for a small client base, the process was not designed to scale as the business grows to 30–50+ clients. Technology decision gap: The team required guidance on choosing between SSRS and Power BI Paginated Reports, along with future automation capabilities. As a result, the organization needed a solution that addressed current inefficiencies while preparing for future scale. The Solution CloudFronts implemented Power BI Paginated Reports, integrated with Dynamics 365 CRM, to create structured, print-ready account statements. Technologies Used Dynamics 365 CRM — Source of funding, account, and transaction data Power BI Paginated Reports — Designed pixel-perfect, client-facing statements Power BI Service — Enabled hosting and future automation capabilities What CloudFronts Configured CloudFronts designed a paginated report tailored for client communication, including account summaries, transaction-level details, and allocation tracking. The solution includes parameterized filtering for month, account, and funding status, enabling efficient report generation across multiple clients. The report was built with a strong emphasis on consistency, print-ready formatting, and reusability—ensuring that reports can be generated without redesign as the business grows. CloudFronts also guided the customer in selecting Power BI Paginated Reports over SSRS to ensure better alignment with the Power BI ecosystem and support for future automation such as subscription-based PDF delivery. Key Implementation Decisions Replacing Excel with Paginated Reports: Improved standardization and reduced manual effort. Choosing Paginated Reports over SSRS: Enabled seamless integration with Power BI Service and future automation readiness. Designing for scalability: Built a solution that works manually today but supports automation in the future. Business Impact Metric Before After Report Creation Manual Excel-based System-generated reports Operational Efficiency Low Significantly improved Scalability Limited Ready for growth Consistency Variable Standardized The organization now operates with a structured reporting system that reduces manual effort while being fully prepared for future automation. Frequently Asked Questions Should I use SSRS or Power BI Paginated Reports? If you are using Power BI, Paginated Reports are a better choice due to seamless integration and future automation support. Can I automate PDF report delivery later? Yes. Paginated Reports support subscription-based delivery for automated PDF emails. Do I need automation from day one? No. It is more effective to design a scalable solution first and introduce automation as the business grows. Conclusion This implementation highlights that effective reporting is not just about automation—it is about designing for scalability from the beginning. By choosing Power BI Paginated Reports, the organization built a solution that meets current needs while avoiding future rework as they grow. Not every reporting requirement needs a dashboard or immediate automation. A well-designed structured report can often be the most scalable solution. Read the full case study here: Invoke We hope you found this article useful. If you would like to explore how AI-powered customer service can improve your support operations, please contact us at transform@cloudfronts.com. Deepak Chauhan | Consultant, CloudFronts

Summary Many organizations track sales performance using pipeline and won revenue dashboards. However, these views often stop short of showing how much revenue is actually realized. For a services firm based in Houston, Texas, specializing in digital transformation and enterprise security solutions, this gap created challenges in understanding real business performance and tracking commissions accurately. This article explains how a connected sales dashboard was designed to bring together pipeline, contracts, and invoicing—providing a complete view from deal to realized revenue. Sales Performance Dashboard showing pipeline to revenue flow Table of Contents 1. Why This Gap Exists 2. Limitation of Traditional Sales Dashboards 3. From Pipeline to Payment 4. Designing the Dashboard 5. The Value of a Unified View 6. The Outcome Why This Gap Exists In many organizations, all sales-related data exists within Dynamics 365 CRM, including opportunities, contracts, order lines, and invoices. However, reporting is often built in stages based on different business needs. Sales teams focus on opportunities and closed deals, while finance teams rely on contract, billing, and invoice data. Over time, separate reports are created for each purpose. While each report works well independently, they are not always connected in a single flow. As a result, answering simple business questions becomes difficult, such as how much of the won revenue is invoiced, which deals are generating actual revenue, and whether commissions are aligned with realized value. Limitation of Traditional Sales Dashboards Most sales dashboards focus on metrics such as won revenue, win rate, deal size, and pipeline value. These provide a good view of sales activity but do not fully reflect business outcomes. A deal marked as won may still be pending contract execution, split across multiple order lines, or not yet invoiced. This creates a disconnect between reported performance and actual revenue realization. As a result, leadership sees growth in numbers, but lacks clarity on how much value has truly been earned. From Pipeline to Payment To address this, the dashboard needs to follow the complete lifecycle of a deal, from opportunity to realized revenue. Opportunity leads to Total Contract Value (TCV), which flows into contracts, then to order lines, followed by invoices, and finally results in realized revenue. Each stage provides a different perspective, ensuring that reporting captures not just intent, but actual business impact. Designing the Dashboard The dashboard was designed in layers to keep it simple while ensuring full visibility across the revenue lifecycle. The first layer provides a snapshot of sales performance, including won revenue, win rate, deal size, deal age, and lost revenue. Supporting visuals such as revenue trends, industry distribution, and geographic spread help leadership understand overall performance and where the business is coming from. The next layer focuses on what drives revenue. By breaking down data across solution areas, industries, regions, and account managers, the dashboard highlights which segments contribute the most and where future efforts should be focused. Once deals are won, contract-level visibility provides clarity on how revenue is structured. It highlights contract types, classifications, and overall value, helping teams understand how revenue will flow from a billing perspective. The dashboard then moves into order line and profitability insights. This layer connects revenue with estimated cost, margin, and profit contribution, allowing the business to evaluate the quality of deals rather than just their size. Finally, invoice-level visibility completes the picture by showing billed amounts, invoice status, and realized revenue. This ensures that the dashboard reflects actual business performance rather than just sales activity. The Value of a Unified View By bringing all these elements together, the organization moved from fragmented reporting to a single, connected view of sales and revenue. This was enabled by combining data across opportunities, contracts, order lines, and invoices into a unified reporting model :contentReference[oaicite:0]{index=0} The result is improved visibility, better alignment between teams, and more reliable decision-making. The Outcome 1. Clear visibility from pipeline to realized revenue 2. Improved alignment between sales and finance teams 3. Better tracking of commissions based on actual performance 4. Reduced manual effort in reconciling multiple reports We hope you found this blog useful. If you would like to learn more or discuss similar solutions, feel free to reach out to us at transform@cloudfronts.com.

Why Incremental Loads Matter When integrating data from external systems, whether it’s a CRM, an ERP like Business Central, or an HR platform like Zoho People, pulling all data every time is expensive, slow, and unnecessary. The smarter approach is to track what has changed since the last successful run and fetch only that delta. This is the core idea behind an incremental data pipeline: identify a timestamp or sequence field in your source system, persist the last-known watermark, and use it as a filter on your next API call. Azure Logic Apps, paired with Azure Table Storage as a lightweight checkpoint store, gives you everything you need to implement this pattern without managing any infrastructure. Architecture Overview Instead of one large workflow doing everything, we separate responsibilities. One Logic App handles scheduling and orchestration. Another handles actual data extraction. Core components: 3. Metadata Design (Azure Table) Instead of hardcoding entity names and fields inside Logic Apps, we define them in Azure Table Storage. Example structure: PartitionKey RowKey IncrementalField displayName entity businesscentral 1 systemCreatedAt Vendor Ledger Entry vendorLedgerEntries zohopeople 1 modifiedtime Leave leave Briefly, this table answers three questions: – What entity should be extracted?– Which column defines incremental logic?– What was the last successful checkpoint? When you want to onboard a new entity, you add a row. No redesign needed. 4. Logic App 1 – Scheduler Trigger: Recurrence (for example, every 15 minutes) Steps: This Logic App should not call APIs directly. Its only job is orchestration. Keep it light. 5. Logic App 2 – Incremental Processor Trigger: HTTP (called from Logic App 1) Functional steps: Example: This is where the real work happens. 6. Checkpoint Strategy Each entity must maintain: – LastSuccessfulRunTime– Status– LastRecordTimestamp After successful extraction: Checkpoint = max(modifiedOn) from extracted data. This ensures: Checkpoint management is the backbone of incremental loading. If this fails, everything fails. This pattern gives you a production-grade incremental data pipeline entirely within Azure’s managed services. By centralizing entity configuration and watermarks in Azure Table Storage, you create a data-driven pipeline where adding a new integration is as simple as inserting a row — no code deployment required. The two-Logic-App architecture cleanly separates orchestration from execution, enables parallel processing, and ensures your pipeline is resilient to failures through checkpoint-based watermark management. Whether you’re pulling from Business Central, Zoho People, or any REST API that exposes a timestamp field, this architecture scales gracefully with your data needs. Explore the case study below to learn how Logic Apps were implemented to solve key business challenges: Ready to deploy AIS to seamlessly connect systems and improve operational cost and efficiency? Get in touch with CloudFronts at transform@cloudfronts.com.

From a customer perspective, the hardest part of data engineering isn’t building pipelines-it’s ensuring that the data customers rely on is accurate, consistent, and trustworthy. When reports show incorrect revenue or missing customer information, confidence drops quickly. This is where Delta Live Tables in Databricks makes a real difference for customers. Instead of customers dealing with broken dashboards, manual fixes in BI tools, or delayed insights, Delta Live Tables enforces data quality at the pipeline level. Using a Bronze–Silver–Gold approach: Data validation rules are built directly into the pipeline, and customers gain visibility into data quality through built-in monitoring-without extra tools or manual checks. Quick Preview Building data pipelines is not the difficult part. The real challenge is building pipelines that are reliable, monitored, and enforce data quality automatically. That’s where Delta Live Tables in Databricks makes a difference. Instead of stitching together notebooks, writing custom validation scripts, and setting up separate monitoring jobs, Delta Live Tables lets you define your transformations once and handles the rest. Let’s look at a simple example. Imagine an e-commerce company storing raw order data in a Unity Catalog table called: cf.staging.orders_raw The problem? The data isn’t perfect. Some records have negative quantities. Some orders have zero amounts. Customer IDs may be missing. There might even be duplicate order IDs. If this raw data goes straight into reporting dashboards, revenue numbers will be wrong. And once business users lose trust in reports, it’s hard to win it back. Instead of fixing issues later in Power BI or during analysis, we fix them at the pipeline level. In Databricks, we create an ETL pipeline and define a simple three-layer structure: Bronze for raw data, Silver for cleaned data, and Gold for business-ready aggregation. The Bronze layer simply reads from Unity Catalog: Nothing complex here. We’re just loading data from Unity Catalog. No manual dependency setup required. The real value appears in the Silver layer, where we enforce data quality rules directly inside the pipeline: Here’s what’s happening behind the scenes. Invalid rows are automatically removed. Duplicate orders are eliminated. Data quality metrics are tracked and visible in the pipeline UI. There’s no need for separate validation jobs or manual checks. This is what simplifies pipeline development. You define expectations declaratively, and Delta Live Tables enforces them consistently. Finally, in the Gold layer, we create a clean reporting table: At this point, only validated and trusted data reaches reporting systems. Dashboards become reliable. Delta Live Tables doesn’t replace databases, and it doesn’t magically fix bad source systems. What it does is simplify how we build and manage reliable data pipelines. It combines transformation logic, validation rules, orchestration, monitoring, and lineage into one managed framework. Instead of reacting to data issues after reports break, we prevent them from progressing in the first place. For customers, trust in data is everything. Delta Live Tables helps organizations ensure that only validated, reliable data reaches customer-facing dashboards and analytics. Rather than reacting after customers notice incorrect numbers, Delta Live Tables prevents poor-quality data from moving forward. By unifying transformation logic, data quality enforcement, orchestration, monitoring, and lineage in one framework, it enables teams to deliver consistent, dependable insights. The result for customers is simple: accurate reports, faster decisions, and confidence that the data they see reflects reality. 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.

For growing businesses, while Power BI solutions are critical, development efficiency becomes equally important-without breaking the budget. As organizations scale their BI implementations, the need for advanced, free development tools increases, making smart tool selection essential to maintaining a competitive advantage Tool #1: DAX Studio – Your Free DAX Development Powerhouse What Makes DAX Studio Essential DAX Studio is one of the most critical free tools in any Power BI developer’s arsenal. It provides advanced DAX development and performance analysis capabilities that Power BI Desktop simply cannot match. Scenarios & Use Cases For a global oil & gas solutions provider with a presence in six countries, we used DAX Studio to analyze model size, reduce memory consumption, and optimize large datasets—preventing refresh failures in the Power BI Service. Tool #2: Tabular Editor 2 (Community Edition) – Free Model Management Tabular Editor 2 Community Edition provides model development capabilities that would cost thousands of dollars in other platforms-completely free. Key Use Cases We used Tabular Editor daily to efficiently manage measures, hide unused columns, standardize naming conventions, and apply best-practice model improvements across large datasets. This avoided repetitive manual work in Power BI Desktop for one of Europe’s largest laboratory equipment manufacturers. Tool #3: Power BI Helper (Community Edition) – Free Quality Analysis Power BI Helper Community Edition provides professional model analysis and documentation features that rival expensive enterprise tools. Key Use Cases For a Europe-based laboratory equipment manufacturer, we used Power BI Helper to scan reports and datasets for common issues-such as unused visuals, inactive relationships, missing descriptions, and inconsistent naming conventions-before promoting solutions to UAT and Production. Tool #4: Measure killer Measure Killer is a specialized tool designed to analyze Power BI models and identify unused or redundant DAX measures, helping improve model performance and maintainability. Key Use Cases For a technology consulting and cybersecurity services firm based in Houston, Texas (USA), specializing in modern digital transformation and enterprise security solutions, we used Measure Killer across Power BI engagements to quickly identify and remove unused measures and columns-ensuring optimized, maintainable models and improved report performance for enterprise clients. To conclude, I encourage you to start building your professional Power BI toolkit today-without any budget constraints. Identify your biggest daily frustration, whether it’s DAX debugging, measure management, or model optimization. Once you see how free tools can transform your workflow, you’ll naturally want to explore the complete toolkit. 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

As data platforms mature, teams often face a familiar question:Should we continue with classic ETL pipelines, or move to Delta Live Tables (DLT)? Both approaches work. Both are widely used. The real challenge is knowing which one fits your use case, not which one is newer or more popular. In this blog, I’ll break down Delta Live Tables vs classic ETL from a practical, project-driven perspective, focusing on how decisions are actually made in real data engineering work. Classic ETL in Databricks Classic ETL in Databricks refers to pipelines where engineers explicitly control each stage of data movement and transformation. The pipeline logic is written imperatively, meaning the engineer decides how data is read, processed, validated, and written. Architecturally, classic ETL pipelines usually follow the Medallion pattern: Each step is executed explicitly, often as independent jobs or notebooks. Dependency management, error handling, retries, and data quality checks are all implemented manually or through external orchestration tools. This approach gives teams maximum freedom. Complex ingestion logic, conditional transformations, API integrations, and custom performance tuning are easier to implement because nothing is abstracted away. However, this flexibility also means consistency and governance depend heavily on engineering discipline. We implemented a Classic ETL pipeline in our internal Unity Catalog project, migrating 30+ Power BI reports from Dataverse into Unity Catalog to enable AI/BI capabilities. This architecture allows data to be consumed in two ways – through an agentic AI interface for ad-hoc querying and through Power BI for governed, enterprise-grade visualizations. We chose the ETL approach because it provides strong data quality control, schema stability, and predictable performance at scale. It also allows us to apply centralized transformations, enforce governance standards, optimize storage formats, and ensure consistent semantic models across reporting and AI workloads -making it ideal for production-grade analytics and enterprise adoption. Delta Live Tables Delta Live Tables is a managed, declarative pipeline framework provided by Databricks. Instead of focusing on execution steps, DLT encourages engineers to define what tables should exist and what rules the data must satisfy. From an architectural perspective, DLT formalizes the Medallion pattern. Pipelines are defined as a graph of dependent tables rather than a sequence of jobs. Databricks automatically understands lineage, manages execution order, applies data quality rules, and provides built-in monitoring. DLT pipelines are particularly well-suited for transformation and curation layers, where data is shared across teams and downstream consumers expect consistent, validated datasets. The platform takes responsibility for orchestration, observability, and failure handling, reducing operational overhead. In my next blog, I will demonstrate how to implement Delta Live Tables (DLT) in a hands-on, technical way to help you clearly understand how it works in real-world scenarios. We will walk through the creation of pipelines, data ingestion, transformation logic, data quality expectations, and automated orchestration. The Core Architectural Difference The fundamental difference between classic ETL and Delta Live Tables is how responsibility is divided between the engineer and the platform. In classic ETL, the engineer owns the full lifecycle of the pipeline. This provides flexibility but increases maintenance cost and risk. In Delta Live Tables, responsibility is shared: the engineer defines structure and intent, while Databricks enforces execution, dependencies, and quality. This shift changes how pipelines are designed. Classic ETL is optimized for control and customization. Delta Live Tables is optimized for consistency, governance, and scalability. When Classic ETL Makes More Sense Classic ETL is a strong choice when pipelines require complex logic, conditional execution, or tight control over performance. It is well suited for ingestion layers, API-based data sources, and scenarios where transformations are highly customized or experimental. Teams with strong engineering maturity may also prefer classic ETL for its transparency and flexibility, especially when governance requirements are lighter. When Delta Live Tables Is the Better Fit Delta Live Tables excels when pipelines are repeatable, standardized, and shared across multiple consumers. It is particularly effective for silver and gold layers where data quality, lineage, and operational simplicity matter more than low-level control. DLT is a good architectural choice for enterprise analytics platforms, certified datasets, and environments where multiple teams rely on consistent data definitions. A Practical Architectural Pattern In real-world platforms, the most effective design is often hybrid. Classic ETL is used for ingestion and complex preprocessing, while Delta Live Tables is applied to transformation and curation layers. This approach preserves flexibility where it is needed and enforces governance where it adds the most value. To conclude, Delta Live Tables is not a replacement for classic ETL. It is an architectural evolution that addresses governance, data quality, and operational complexity. The right question is not which tool to use, but where to use each. Mature Databricks platforms succeed by combining both approaches thoughtfully, rather than forcing a single pattern everywhere. Choosing wisely here will save significant rework as your data platform grows. Need help deciding which approach fits your use case? Reach out to us at transform@cloudfronts.com