Working with Microsoft Dataverse Connector in Power BI is usually straightforward—until you encounter a table that simply refuses to load any rows, even though the data clearly exists in the environment. This happens especially with hidden, virtual, or system-driven tables (e.g. msdyn_businessclosure, msdyn_scheduleboardsetting) which are commonly used in Field Service and Scheduling scenarios. Before jumping to a workaround, it’s important to understand why certain Dataverse tables don’t load in Power BI, what causes this behavior, and why the standard Dataverse connector may legitimately return zero rows. Causes – 1] The Table Is a Virtual or System Table with Restricted AccessSystem-managed Dataverse tables like msdyn_businessclosure are not exposed to the Dataverse connector because they support internal scheduling and platform functions. 2] No Records Exist in the Root Business Unit Data owned by child business units is not visible to Power BI accounts associated with a different BU, resulting in zero rows returned. 3] The Table Is Not Included in the Standard Dataverse Connector Some solution-driven or non-standard tables are omitted from the Dataverse connector’s supported list, so Power BI cannot load them. Solution: Export Dataverse Data Using Power Automate + Excel Sync Since Power BI can read:-> OneDrive-hosted files-> Excel files-> SharePoint-hosted spreadsheets …a suitable workaround is to extract the restricted Dataverse table into Excel using a scheduled (When the records are few) / Dataverse triggered (When there are many records and you only want a single one, to avoid pagination) Power Automate flow. What it can do –-> Power Automate can access system-driven tables.-> Excel files in SharePoint can be refreshed by Power BI Service.-> we can bypass connector restrictions entirely.-> The method works even if entities have hidden metadata or internal platform logic. This ensures:-> Consistent refresh cycles-> Full visibility of all table rows-> No dependency on Dataverse connector limitations Use case I needed to use the Business Closures table (Dataverse entity: msdyn_businessclosure) for a few calculations and visuals in a Power BI report. However, when I imported it through the Dataverse Connector, the table consistently showed zero records, even though the data was clearly present inside Dynamics 365. There are 2 reasons possible for this –1] It is a System/Platform Tablemsdyn_businessclosure is a system-managed scheduling table, and system tables are often hidden from external connectors, causing Power BI to return no data. 2] The Table Is Not Included in “Standard Tables” Exposed to Power BIMany internal Field Service and scheduling entities are excluded from the Dataverse connector’s metadata, so Power BI cannot retrieve their rows even if they exist. So here, we would fetch the records via “Listing” in Power automate and write to an excel file to bypass the limitations that hinder the exposure of that data; without compromising on user privileges, or system roles; we can also control or filter the rows being referred directly at source before reaching PBI Report. Automation steps – 1] Select a suitable trigger to fetch the rows of that entity (Recurring or Dataverse, whichever is suitable). 2] List the rows from the entity (Sort/Filter/Select/Expand as necessary). 3] Perform a specific logic (e.g. clearing the existing rows, etc.) on the excel file where the data would be written to. 4] For each row in the Dataverse entity, select a primary key (e.g. the GUID), provide the path to the particular excel file (e.g. SharePoint -> Location -> Document Library -> File Name -> Sheet or Table in the Excel File), & assign the dynamic values of each row to the columns in the excel file. 5] Once this is done, import it to the PBI Report by using suitable Power Query Logic in the Advanced Editor as follows – -> a) Loading an Excel File from SharePoint Using Web.Contents() – Source = Excel.Workbook(Web.Contents(“https://<domain>.sharepoint.com/sites/<Location>/Business%20Closures/msdyn_businessclosures.xlsx”),null,true), What this step does: -> Uses Web.Contents() to access an Excel file stored in SharePoint Online.-> The URL points directly to the Excel file msdyn_businessclosures.xlsx inside the SharePoint site.-> Excel.Workbook() then reads the file and returns a structured object containing:All sheets, Tables, Named ranges Parameters used: null → No custom options (e.g., column detection rules)true → Indicates the file has headers (first row contains column names) -> b) Extracting a Table Named “Table1” from the Workbook – msdyn_businessclosures_Sheet = Source{[Item=”Table1″, Kind=”Table”]}[Data], This would search inside the Source object (which includes all workbook elements), and look specifically for an element where: Item = “Table1” → the name of the table in the Excel fileKind = “Table” → ensures it selects a table, not a sheet with the same name & would extract only the Data portion of that table. As a result, we get Power Query table containing the exact contents of Table1 inside the Excel workbook, to which we can further apply our logic filter, clean, etc. To conclude, when Dataverse tables refuse to load through the Power BI Dataverse Connector—especially system-driven entities like msdyn_businessclosure—the issue is usually rooted in platform-level restrictions, connector limitations, or hidden metadata. Instead of modifying these constraints, offloading the data through Power Automate → Excel → Power BI provides a controlled, reliable, and connector-independent integration path. By automating the extraction of Dataverse rows into an Excel file stored in SharePoint or OneDrive, you ensure: This method is simple to build, stable to maintain, and flexible enough to adapt to any Dataverse table -whether standard, custom, or system-managed. For scenarios where Power BI needs insights from hidden or restricted Dataverse tables, this approach remains one of the most practical and dependable solutions. 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.

Tax Deducted at Source (TDS) with concessional rates on threshold limits is a provision that enables eligible taxpayers to benefit from lower TDS rates, as permitted by government-issued certificates. These certificates are granted to individuals or entities that meet specific criteria, such as lower tax liability or involvement in designated transactions. By implementing concessional rates, taxpayers can effectively manage their immediate tax burden, enhance cash flow, and ensure compliance with regulatory requirements. This guide outlines the step-by-step process for configuring concessional TDS rates in Microsoft Dynamics 365 Finance & Operations (D365 F&O) to facilitate accurate tax calculations and ensure seamless compliance. Step-by-Step Configuration of TDS in D365 F&O 1. Setting Up the Withholding Tax Code Navigate to Tax → Indirect Taxes → Withholding Tax → Withholding Tax Code and either select an existing tax code or create a new one. Ensure all required details are entered accurately. 2. Defining Concessional TDS Rates Click on Values and insert the applicable TDS rates as per government guidelines. 3. Configuring Threshold Limits Access Tax → Indirect Taxes → Withholding Tax → Withholding Tax Code and select Threshold Designer. Enter the threshold limits for TDS rates, specifying the applicable conditions when these limits are reached. 4. Establishing Post-Threshold Tax Treatment Provide details regarding the applicable tax rate once the threshold limit is exceeded to ensure proper compliance. 5. Assigning Threshold References Navigate to Tax → Indirect Taxes → Withholding Tax → Withholding Tax Code and select Threshold Reference. Assign the relevant Vendor, specific group, and threshold code to ensure accurate tax calculations. 6. Creating a TDS Group Define a new TDS Group and link it with the recently created withholding tax code to streamline tax application across transactions. 7. Configuring the Tax Code in Designer Use the Designer tool to reassign the withholding tax code, ensuring correct integration within tax processing workflows. 8. Associating the Tax Group with Vendors Assign the defined Tax Group to the relevant vendor. Once this is set up, proceed with Vendor Invoice postings or Purchase Order creation, ensuring that the concessional TDS rates are accurately applied to financial transactions. Proper configuration of TDS with concessional rates in D365 F&O ensures compliance with tax regulations while optimizing cash flow for eligible taxpayers. By implementing the correct withholding tax setup, organizations can streamline their tax processes and minimize unnecessary deductions. This structured approach enhances financial accuracy and simplifies tax management, contributing to more efficient business operations. 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

In modern business settings, employees spend a significant portion of their time searching for information rather than using it. According to Microsoft, office workers can spend up to 20 % of their working time simply looking for data. With the “Search in company data” feature in Business Central, organizations can now provide users with faster, broader, and more relevant search capabilities—giving them more time to focus on strategic tasks rather than just data retrieval. Using this feature is straightforward and intuitive. You can either highlight any text within Business Central and open the Tell Me window, or type one or more keywords directly into it. Then, select the Search company data option to explore matching information across your system. So instead of opening Item list page and searching item name you can simply use above option. Once you click on Search Company Data it will open Search result with new page. You can simply click on result to open searched item page. You can enable more table to search across them by clicking “Setup where to search” option. To conclude, the Search in Company Data feature in Microsoft Dynamics 365 Business Central empowers users to find information faster and more efficiently. Instead of navigating through multiple pages or lists, users can now access the data they need directly through the Tell Me window. With the added flexibility to configure which tables and fields are searchable, organizations can tailor the experience to meet their specific needs. By simplifying the search process and enabling broader data accessibility, this feature not only saves time but also enhances productivity-allowing users to focus on decision-making and value-driven tasks rather than manual data lookups. 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

The landscape of digital transformation has never been more complex. Rapid market shifts, rising customer demands, and tightening budgets have made technology decisions more consequential than ever. The challenge isn’t adopting new tools it’s leading transformation by ensuring that every investment is grounded in clarity, alignment, and predictability. At CloudFront’s, we understand this. That’s why our Business Assessment Engagement model has become a proven first step toward successful, low-risk technology implementations. What Is a Business Assessment? A Business Assessment is a structured, short-term engagement conducted before signing a full implementation Statement of Work (SoW). It is designed to create complete visibility into your current business processes, desired future state, and the potential risks that could impact your project. Typically spanning 3 – 4 weeks, this engagement brings together functional and technical stakeholders from both your organization and CloudFront’s. Whenever feasible, we conduct this assessment onsite, ensuring close collaboration and a deep understanding of your business landscape. During this engagement, our experts: The result is a detailed Business Requirements Study (BRS) a comprehensive document that translates assessment insights into an actionable implementation roadmap. This BRS becomes the foundation for a precise and mutually agreed Statement of Work, ensuring every phase of your digital transformation is built on validated insights and shared understanding. Why a Business Assessment Matters For enterprise technology leaders, the Business Assessment approach delivers tangible benefits: Ultimately, this process transforms uncertainty into informed decision-making, enabling IT leaders to confidently advance from planning to execution. Proven Success with CloudFront’s At CloudFront’s, we’ve seen firsthand how Business Assessment engagements set the stage for successful digital transformations. Clients who adopt this model enter implementation phases with greater predictability, stronger governance, and renewed confidence in both the technology and the partnership driving it. Recently, we partnered with one of the world’s largest U.S. based commercial vehicle manufacturers to conduct an onsite Business Requirements Study (BRS). Our team worked closely with their stakeholders to map existing systems and design a strategic roadmap for migration to Microsoft Dynamics 365 Supply Chain Management (SCM). Following the successful completion of the BRS, we are now leading Phase 1, enabling their inventory, advanced warehouse, and procurement operations to establish a strong operational foundation. In Phase 2, we will enable master planning, production, and quality management to deliver end-to-end operational efficiency, ensuring a seamless and future-ready digital ecosystem. Our clients consistently tell us that this approach not only de-risks their investment but also enhances alignment between business and IT, a crucial factor in any transformation journey. To conclude, in today’s unpredictable business landscape, a well-executed Business Assessment isn’t just a preliminary step, it’s a strategic imperative. By partnering with CloudFront’s for a Business Assessment, you’re not committing to uncertainty; you’re investing in clarity, alignment, and long-term success. If your organization is planning a digital transformation initiative, start with a Business Assessment Engagement and move forward with the confidence of knowing your path is mapped, risks are managed, and success is measurable. Ready to move from uncertainty to clarity?Connect with CloudFront’s at transform@cloudfronts.com to schedule a Business Assessment Engagement and gain a clear, actionable roadmap for your next digital transformation. Contact Us to start your assessment today.

For any Indian business running on Microsoft Dynamics 365 Business Central, tax compliance isn’t optional, it’s foundational. The Goods and Services Tax (GST) framework is complex and manually managing it is a high-risk gamble. This guide isn’t just a list of steps; it’s your definitive blueprint for configuring Business Central’s powerful Indian localization features to handle GST seamlessly. We will transform your ERP from a standard ledger into a fully automated, compliance-ready machine. Ready to banish tax-related data entry errors and audit anxiety? Let’s dive in and set up the system correctly, from defining your GSTINs to mastering the G/L posting matrix. Microsoft Dynamics 365 Business Central offers robust localization features for India, including comprehensive support for the Goods and Services Tax (GST). Properly configuring GST is essential for calculating, recording, and settling taxes on all your inward and outward supplies, ensuring compliance with Indian tax laws. This guide provides a straightforward, step-by-step process for setting up GST in Business Central, based on Microsoft’s best practices. Phase 1: Laying the Foundation (Tax Periods & Registration) The initial phase involves setting up the legal and temporal frameworks for your GST configuration. Step 1: Define Tax Accounting Periods (GST Calendar) The GST regime operates on a specific timeline, and you need to define this within Business Central. Step 2: Establish Your GST Registration Numbers (GSTINs) Your Goods and Service Tax Payer Identification Number (GSTIN) is critical for identifying your tax entity and the state you operate in. Phase 2: Core Configuration (G/L Accounts and Masters) This phase links the statutory requirements with your company’s general ledger structure. Step 3: Configure GST Groups and HSN/SAC Codes These setups classify your goods and services for accurate rate calculation. Step 4: Define the GST Posting Setup (The Accounting Link) This is perhaps the most crucial step, as it determines which General Ledger (G/L) accounts are used to post GST amounts. Step 5: Set Up GST Rates With your Groups and HSN/SAC codes defined, you now specify the actual tax percentages. Phase 3: Master Data Integration (Connecting the Dots) The final phase ensures that your business entities and locations are linked to the defined GST rules. Step 6: Update Company and Location Information Your company’s primary details must be GST-compliant. Step 7: Configure Customer and Vendor Master Data For every trading partner, you must define their GST status and registration details. To conclude, by following these seven steps, your Indian company’s Business Central environment will be fully configured to handle GST calculations automatically. This setup allows the system to determine the correct tax component (CGST, SGST, or IGST), apply the right rate, and post the amounts to the designated G/L accounts, simplifying your day-to-day transactions and preparing you for GST settlements and reporting. I Hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com.

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

Integrating Dynamics 365 (D365) with external systems using Azure Logic Apps is one of the most common patterns for automation. But in real-world projects, things rarely go smoothly – API throttling, network timeouts, and unexpected data issues are everyday challenges. Without proper error handling and retry strategies, these issues can result in data mismatches, missed transactions, or broken integrations. In this blog, we’ll explore how to handle errors and implement retries in D365 Logic App integrations, ensuring your workflows are reliable, resilient, and production-ready. Core Content 1. Why Error Handling Matters in D365 Integrations Without handling these, your Logic App either fails silently or stops execution entirely, causing broken processes.  2. Built-in Retry Policies in Logic Apps What They Are:Every Logic App action comes with a retry policy that can be configured to automatically retry failed requests. Best Practice: 3. Handling Errors with Scopes and “Run After” Scopes in Logic Apps let you group actions and then define what happens if they succeed or fail. Steps: Example: 4. Designing Retry + Error Flow Together Recommended Pattern: This ensures no transaction is silently lost. 5. Handling Dead-lettering with Service Bus (Advanced) For high-volume integrations, you may need a dead-letter queue (DLQ) approach: This pattern prevents data loss while keeping integrations lightweight. 6. Monitoring & Observability Error handling isn’t complete without monitoring. Building resilient integrations between D365 and Logic Apps isn’t just about connecting APIs—it’s about ensuring reliability even when things go wrong. By configuring retry policies, using scopes for error handling, and adopting dead-lettering for advanced cases, you’ll drastically reduce downtime and data mismatches. Next time you design a D365 Logic App, don’t just think about the happy path. Build error handling and retry strategies from the start, and you’ll thank yourself later when your integration survives the unexpected. 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

For years, Microsoft Dynamics GP has been a reliable ERP system, helping businesses streamline financial operations, maintain compliance, and drive efficiency. It became a backbone for thousands of organizations, particularly mid-sized businesses that valued its stability and robustness. But the business landscape has changed dramatically. Markets move faster. Customer expectations are higher. And technology is no longer just a support function, it is the engine of growth, agility, and innovation. This is why the transition from Dynamics GP to Microsoft Dynamics 365 Business Central is not just another software upgrade. It is a strategic leap forward that determines how ready your business is for the next decade. The Real Question: Maintain or Evolve? Every business leader faces this decision at some point: continue maintaining what’s familiar or evolve into what’s next. GP offers stability, but that stability now comes with limitations, manual upgrades, server costs, and restricted scalability. For many companies, these challenges are becoming a bottleneck to innovation. On the other hand, Business Central offers agility. It’s a modern, cloud-first ERP that grows with your business, continuously innovates, and seamlessly integrates with the entire Microsoft ecosystem. In today’s world, standing still is the same as moving backward. The choice is simple: maintain what works or evolve toward what drives growth. What Businesses Gain with Business Central Always Up to Date No more manual upgrades or disruptive transitions. Business Central runs on the cloud with continuous updates and innovations at no additional cost. This means your team is always using the latest technology, features, and security enhancements without the burden of maintenance. Faster Decisions, Smarter Moves In an age where data drives competitive advantage, Business Central integrates seamlessly with Power BI and embedded analytics to deliver real-time insights. Leaders can act on facts, not assumptions, and empower their teams to make faster, data-driven decisions that move the business forward. Scalability Without Limits Growth brings complexity, new markets, entities, currencies, and compliance requirements. Business Central scales effortlessly to handle it all. Whether you are expanding into new geographies or diversifying your business model, the system grows with you, not against you. An Integrated Digital Workplace Business Central works hand in hand with Microsoft 365, Teams, Power Automate, and AI. The result is a truly connected workplace where data flows freely, collaboration improves, and manual processes give way to automation. This integration not only boosts productivity but also builds a culture of transparency and shared accountability. Cost Efficiency and Risk Reduction By eliminating on-premise IT infrastructure, you reduce overheads, lower downtime, and free up valuable resources to focus on innovation. With built-in security, compliance, and automated backups, your business becomes more resilient and future-proof. A Transformation Story At CloudFronts, we recently began working with a mid-sized client who had been running Dynamics GP for nearly three decades. GP had been the financial backbone of their operations and had served them well. However, the leadership team recognized an emerging reality: GP will soon reach its end of life, and continuing to rely on it would increase both operational risk and cost. They made a strategic decision, to migrate to Business Central and secure a platform built for the next decade of growth. Their goals were clear: This migration is now underway, and the client views it not as an IT project, but as a business transformation initiative. For them, Business Central represents the foundation of a connected, intelligent enterprise, one where decisions are faster, processes are leaner, and growth is continuous. Why Now Is the Right Time Many businesses delay ERP migrations because “things are working fine.” But the reality is that postponing the move comes with hidden risks, rising IT maintenance costs, outdated security models, dependency on legacy infrastructure, and the gradual loss of talent familiar with older systems. At the same time, competitors who embrace modern ERP platforms are moving faster, integrating AI, automating workflows, and leveraging real-time insights. The cost of waiting is not just financial, it is strategic. Business Central is more than an ERP. It is a platform for growth, intelligence, and resilience. It enables organizations to future-proof their operations while staying agile in an unpredictable world. The Takeaway Migrating from GP to Business Central is not a technical move-it is a business transformation decision. It means: With Dynamics GP approaching its end of life, the question is not if you should move, but when and how strategically you make that move. The time to act is now. If you are evaluating your options or planning your next steps, let’s talk. At CloudFronts, we’ve helped businesses across industries transition from legacy ERP systems to modern, scalable platforms like Business Central with minimal disruption and maximum value. Reach out at transform@cloudfronts.com. Let’s explore how you can evolve confidently into the future of business.

This blog provides a comprehensive, step-by-step guide for performing a year-end close in Microsoft Dynamics 365 Finance and Operations (F&O). It includes instructions, common issues, and suggestions for extracting relevant screenshots from a demo environment. 1. Pre-Close Activities 2. Performing the Year-End Close A. Set Up the Fiscal Year End Parameters B. Perform the Year-End Close Process C. Review Results D. Post-Close Activities 3. Common Issues and Tips Issue Action Profit and Loss accounts didn’t zero out Check ledger account settings. Retained Earnings entry missing Verify Retained Earnings account in ledger setup. Incorrect balances after year-end close Use the “Reverse” option and review postings. User doesn’t have access Ensure role has Financial Period Close privileges. Ledger Calendar page Performing the year-end close in D365 F&O is a structured process that ensures data integrity across financial periods. 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

In today’s global manufacturing landscape, businesses need more than just strong products to stay competitive. They need digital operations that connect customers, distributors, and internal teams in different regions. One powerful way to achieve this is by integrating e-commerce platforms with enterprise resource planning (ERP) systems. This is the story of a 140-year-old global leader in materials testing machine manufacturing that transformed its order-taking process through a Shopify–Dynamics 365 Finance & Operations integration. The Challenge With offices in five countries and sales across the UK, Europe, China, India and multiple U.S. territories, this manufacturer had a truly global footprint. Yet, order-taking remained manual and inefficient: In short: their legacy setup couldn’t keep up with modern customer expectations or their own ambitions for global growth. The Solution Over the course of a decade long partnership, we helped the company modernize and digitize its business processes. The centerpiece was a seamless integration between Shopify and Dynamics 365 Finance & Operations (F&O), built natively within F&O (no recurring middleware costs). Key integrations included: This solution ensured that high data volumes and complex processing demands could be handled efficiently within F&O. The Results The change has reshaped how the company works: Lessons for Other Global Manufacturers This journey highlights critical lessons for manufacturers, distributors, and global businesses alike: The Road Ahead After integrating Shopify with Dynamics 365 F&O, the company has launched a dedicated distributor website where approved distributors can place orders directly on behalf of customers. This portal creates a new revenue stream, strengthens the distribution network, and ensures orders flow into F&O with the same automation, inventory sync, and reporting as direct sales. By extending digital integration to distributors, the company is simplifying order-taking while expanding its business model for global growth. Ending thoughts The journey of this global manufacturer shows that true digital transformation isn’t about adding more tools, it’s about connecting the right ones. By integrating Shopify with Dynamics 365 F&O, they moved from fragmented, manual processes to a scalable, automated ecosystem that empowers customers, distributors, and internal teams alike. For any organization operating across regions, the lesson is clear: e-commerce and ERP should not live in silos. When they work together, they create a foundation that not only accelerates order taking but also unlocks new revenue streams, sharper insights, and stronger global relationships. In a world where speed, accuracy, and customer experience define competitiveness, the question isn’t whether you can afford to integrate, it’s whether you can afford not to. If you need further assistance or have specific questions about your ERP setup, feel free to reach out for personalized guidance.We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com.