One Integration, Two Engines

AstraReports lets you run reports against your Acumatica data using two different engines: SAP Crystal Reports and Microsoft Power BI. They are not competing products you have to choose between once and for all — they are two outputs of the same integration. Both read from Acumatica Generic Inquiries, both are selected through the Report Engine field on the Astra Report Design screen, and both run and preview inside Acumatica. The right question is not “which engine should we standardize on,” but “which engine fits this particular report.”

What the Two Engines Share

Before the differences, it helps to see how much is common. Both engines use a Generic Inquiry as their governed data source rather than raw tables, so the same clean data model can feed either one. Both are configured in the same Pixis workspace, both honor the access rights you set in Report Settings, and both let users run reports without leaving Acumatica. In practice this means a single Generic Inquiry — say, one built on Work Center Dispatch or an AR aging view — can back a Crystal Report for one audience and a Power BI report for another.

When to Choose Crystal Reports

Crystal Reports is the right engine when the output is a document. It excels at pixel-perfect, print-ready layouts where every margin, header, and total lands exactly where it should: financial statements, invoices, purchase orders, checks, and regulatory filings. It is also the natural choice when you already own Crystal Report (.rpt) assets, when you need sub-reports and drill-down links, and when reports are delivered on a schedule by email to stakeholders. For controllers and finance teams who care about formatting precision and repeatable document output, Crystal Reports remains the workhorse.

When to Choose Power BI

Power BI is the right engine when the output is an experience. It shines for interactive dashboards, visual analytics, and data exploration where users filter, slice, and drill into the numbers themselves rather than reading a fixed page. Because AstraReports publishes Power BI content into a Microsoft Fabric workspace, Power BI is also the natural fit for organizations already invested in the Microsoft data ecosystem, and its paginated reports cover cases where you still want a structured, multi-page layout. For operations teams and analysts who want to see trends and ask follow-up questions, Power BI is the stronger tool.

A Simple Way to Decide

If the report will be printed, emailed on a schedule, or needs exact formatting, reach for Crystal Reports. If the report will be explored on screen, filtered by the viewer, or lives alongside other Microsoft Fabric content, reach for Power BI. And when a single data source serves both needs, remember you can build it twice on the same Generic Inquiry — once per engine — without duplicating your data work.

Getting Started

If you are new to the Power BI engine, start with “Setting Up Power BI Integration with Acumatica” to connect your tenant, then follow “Building Power BI Reports in AstraReports” to publish your first paginated report. Your existing Crystal Reports keep working exactly as before.