Best Copilot prompts for Dynamics 365 Business Central analysis views 

Microsoft Dynamics 365 Business Central continues to evolve as a modern, data-driven ERP platform. One of the most meaningful recent enhancements is the introduction of Copilot within analysis views, allowing users to explore data using natural language instead of manually building filters and pivots. 

For organizations moving from Dynamics GP or relying heavily on Excel exports, this shift is significant. Analysis mode in Business Central, enhanced with Copilot, is Microsoft’s effort to enable ad hoc reporting directly inside the ERP. It is not flawless, and it does not replace formal reporting tools. But it is improving with every release and already delivering measurable value. 

In this blog, we will explore practical Copilot prompts across key Business Central entities, highlight where it performs well, identify limitations to watch for, and provide guidance on how to use it strategically in production environments. 

Understanding analysis views and Copilot in Dynamics 365 Business Central 

Copilot in analysis mode works by interpreting natural language prompts and restructuring the current list page accordingly. When you select Analyze list and enter a prompt, Copilot can: 

• Select relevant fields from the current table 
• Apply filters based on numeric or date logic 
• Switch to pivot mode when grouping is implied 

However, it operates within defined boundaries. Copilot can only use fields available on the page or table you are currently viewing. It does not yet perform true table joins across unrelated entities, and some advanced filtering scenarios, such as Top N logic, may not be supported depending on the dataset. Success with Copilot depends on two things: asking the right business question and starting from the right table. 

Customer analysis prompts for Copilot in Dynamics 365 Business Central

Customer analysis is often the simplest place to begin. Because balance-related data lives directly on the customer record, Copilot can interpret straightforward financial prompts effectively. 

For example, asking to see customers with balances greater than a specific threshold typically results in: 

• The Balance field being added to the view 
• A filter applied to show only customers above that threshold 
• A sortable list ready for refinement 

This is where Copilot shines, translating plain language into filters that would otherwise require manual configuration. As with any AI-driven capability, the quality of the prompt directly influences the quality of the result. Clear, specific language produces more reliable analysis structures and filters. For a deeper look at how to craft more effective AI prompts, explore our guide on practical AI prompt engineering techniques.

That said, users must validate which balance field is being used. “Balance” and “Balance due” are not always identical in production environments. Additionally, if the business question involves aging buckets or year-based comparisons, the customer master record alone will not support that analysis. When time-based insight is required, the correct starting point is usually posted sales invoices. 

Vendor spend analysis prompts for Copilot in Dynamics 365 Business Central

Vendor analysis highlights both the promise and the limitations of Copilot. 

If a user requests vendor spend by year from the Vendors list page, Copilot may attempt to interpret “spend” using fields such as Balance, or apply date logic based on last modified date. While the layout may look polished, it may not reflect the actual financial question being asked. 

The reason is structural: the vendor record does not inherently contain detailed transactional spend history with usable date context. 

To analyze vendor spend effectively, users often need to: 

• Replace balance-related fields with Payments or invoice totals 
• Remove irrelevant columns from the view 
• Filter out zero-value entries 

More importantly, when analyzing spend by year, the correct table is typically Posted Purchase Invoices. Invoice header records contain proper date fields that support year-based grouping and filtering. Copilot accelerates setup, but users must understand where the data lives. 

Item profitability and pivot analysis

Items are a strong use case for Copilot because many profitability metrics exist directly on the item master. If a user asks to see the most profitable items, Copilot will generally add profit percentage or related fields and structure the view for analysis. However, it may not apply a true Top N filter because that functionality is not always supported within analysis filters. 

Where Copilot becomes particularly useful is pivot manipulation. Users can ask to pivot by item category or adjust row and column orientation, and Copilot will switch into pivot mode automatically. 

This is valuable for teams that are less comfortable building pivot tables manually. Instead of rearranging fields through trial and error, they can refine the view conversationally. For example, adjusting whether category appears in rows or columns becomes a simple prompt rather than a technical task. The result is faster insight with fewer manual steps. 

Sales analysis by customer and year 

Time-based sales analysis requires starting from the right dataset. Running year-over-year sales from the Customers page will not work effectively because date fields are not structured for that purpose. 

From the Posted Sales Invoices page, however, Copilot can: 

• Group sales amounts by customer 
• Extract year from the posting date 
• Pivot year across columns for comparison 

Users may still need to refine the layout by adding document numbers for drilldowns or removing unnecessary contextual fields. Sorting may also require adjustment to ensure chronological order. 

Recent updates have improved how Copilot handles year sorting, reducing earlier inconsistencies. Even so, reviewing the pivot structure before sharing results is a recommended practice. For organizations transitioning from Dynamics GP, this capability helps replace SmartList-style inquiries while offering more flexibility through pivot views. 

Sales invoice line analysis for product insights 

When analyzing revenue by product and customer, Posted Sales Invoice Lines often provide the most detailed insight. 

A prompt requesting product sales by revenue and customer may produce a pivoted layout with items summarized and zero-value lines filtered automatically. However, date-based filtering may be limited if relevant date fields are not visible on the page. 

Users can refine the results by: 

• Repositioning item and customer fields 
• Removing metrics that are not relevant to the analysis 
• Adjusting pivot orientation for readability 

Copilot may not build the exact layout desired on the first attempt. But it provides a structured foundation that reduces the time required to build analysis views manually. For operational leaders who need quick answers without exporting to Excel, this is a meaningful efficiency gain. 

General ledger analysis using Copilot in Dynamics 365 Business Central

General ledger analysis requires a slightly different approach. Copilot is not directly available from the Chart of Accounts page in the same way it is from list views. Instead, analysis is typically performed from the General Ledger Entries page. 

If a user asks for advertising expense over the last 12 months, and “Advertising” matches a G/L account name, Copilot can filter to the correct account and apply a date range. 

However, there are important considerations: 

• Relative date logic may convert into fixed date ranges 
• Copilot may initially select an unintended account 
• Pivot sorting may require manual correction 

If account naming does not align with business terminology, Copilot may struggle to interpret the request. This makes structured chart of accounts design even more important when leveraging AI-assisted analysis. Once refined, these views can be saved and reused, allowing finance teams to revisit frequently used inquiries without rebuilding them each time. 

Practical limitations to understand 

Copilot in analysis views is powerful, but it is not a replacement for structured reporting or BI platforms. Current limitations include limited Top N filtering, no full table joins across unrelated datasets, and dependence on visible page fields. In some cases, Copilot may retain elements from earlier prompts unless explicitly removed. 

Microsoft continues to invest heavily in this area, and enhancements around table joins and expanded data awareness are expected in upcoming releases. Many organizations pair Copilot with broader Business Central optimization strategies, including workspace personalization, saved views, automation, and embedded analytics. For more practical ways to streamline daily work inside the ERP, see these Dynamics 365 Business Central tips and tricks to increase productivity.

Strategic implications for Dynamics 365 Business Central users 

Copilot-enabled analysis views represent a shift in how users interact with ERP data. Instead of exporting to Excel, users can stay within Business Central while maintaining role-based security and working with near real-time data. This supports faster inquiry cycles for finance teams, enables operational managers to explore performance metrics independently, and reduces reporting bottlenecks for leadership.

For organizations migrating from Dynamics GP, it also helps bridge the gap left by SmartLists while offering a more modern, pivot-driven interface. As capabilities expand, analysis views with Copilot will increasingly support day-to-day operational insight without requiring external tools. For a broader look at how AI is transforming the platform, explore our overview of practical Copilot use cases in Dynamics 365 Business Central.

Your Dynamics 365 Business Central & Copilot strategy partner

Adopting capabilities like Copilot in Business Central is not simply about enabling a feature. It requires a clear understanding of your data model, reporting structure, governance standards, and long-term Microsoft roadmap. That is where the right partner makes a meaningful difference.

Rand Group is a Microsoft-focused consulting firm with deep expertise in Dynamics 365 Business Central. We help organizations evaluate new functionality within the context of broader financial, operational, and reporting objectives — not as standalone tools.

Our team combines functional and technical knowledge of Business Central with practical experience and a structured approach to reporting design and data governance. We understand the challenges B2B organizations face when reducing Excel dependency, modernizing processes, and empowering users with reliable self-service insights.

Whether you are implementing Business Central, optimizing your reporting strategy, or determining how Copilot fits into your environment, Rand Group serves as a trusted advisor focused on turning Microsoft innovation into practical business value.

Frequently asked questions about Copilot in Business Central analysis views

Next steps

Copilot in Dynamics 365 Business Central analysis views is designed to enhance, not replace, structured reporting. When used strategically, it reduces manual data exports, accelerates analysis, and improves user adoption of native ERP functionality. The key is understanding where data lives, how tables relate to business questions, and when to refine or validate Copilot’s output. 

At Rand Group, we help organizations assess how to leverage Business Central’s evolving AI capabilities while maintaining data integrity and governance. Whether you are transitioning from Dynamics GP, optimizing reporting processes, or evaluating how Copilot fits into your broader Microsoft strategy, our team provides practical, implementation-focused guidance. 

If you would like to explore how Copilot and analysis views can support more efficient reporting in your Business Central environment, contact Rand Group to start a conversation.