There are so many improvements they could make to the report designer, etc that itād be nice to see them actually maintain it for once.
I wonder if theyāll roll report builder into PowerBI reports designer. It creates the new flashy dashboards and stuff.
Kind of? Power BI Report Builder is basically three report designers in a power bi trenchcoat.
Yes, I did mention this during the Q&A. This has been a question that we have been researching for the past 3-5 years. Product management has been pushing for a resolution before it becomes an issue.
Up until a few months ago, every solution we found required significant conversions and/or rewriting of reports. Also know that Kinetic is not the only one involved here. We have many products (P21, Bistrack, Kinetic, iScala, Eclipse, etc) that all have the same challenge: a long list of paginated reports (AR Aging, Inventory, Travelers) and forms (POs, Sales Orders, Invoices, etc) that NEED to be in any business system, and we want a solution that works for all our products.
(INSERT SAFE HARBOR STATEMENT HERE)
We have narrowed the list of potentials down to three⦠but two of them still would require significant work to convert reports from SSRS & Crystal (yes, some of our products also still use Crystal). One solution came out the clear winner from a technological standpoint, requiring very little (if any) changes to support our current reports, (and your current customizations). We hope to have something to announce in the next few months.
But rest assured, I know that I will be one of the people standing in front of you all at some user group meeting or Insights, making the announcement, and I want that announcement to receive a response of cheers
(not jeers
). I do not want to be a target for
tomato throwing
(INSERT SAFE HARBOR STATEMENT HERE)
I donāt know, that tomato throwing festival looks pretty lit.
I was part of the private preview beta testing for SQL 2025 as I hope some of you here (and Epicor) have been as well. We are looking at upgrading all of our databases (Kinetic and others) to SQL 2025 when it becomes GA. Conversations during beta testing about reporting services were a major concern. If you so desire, I donāt think migrating to PBIRS will be that big of an issue (at least for us on prem users). You can still use SSRS, but there just wonāt be a new version. We upgraded to 2025.1.5 recently and I saw that the installation document only shows the following valid O/S configurations on page 10 of the installation guide:
Verifying Windows Operating System Requirements:
Windows Server 2022 with SQL Server 2019 or 2022
Windows Server 2025 with SQL Server 2022
On page 20 which specifies valid SQL Server configurations, they also have the valid SQL Server configurations that are the same:
Microsoft SQL Server:
Windows Server 2022 with SQL Server 2019 or 2022
Windows Server 2025 with SQL Server 2022
BUT⦠Also on page 20, the installation document has the following configurations for the optional SQL features that must be installed:
Verify the following required and optional SQL Server features are installed:
Database Engine Services:
SQL Server Replication (optional, but recommended with most deployments with certain
3rd party products such as Advanced Financial Reporting)
Reporting Services:
Either SQL Server Reporting Services (SSRS) 2019 with SQL Server 2019, SSRS 2022 with
SQL Server 2022, or SSRS 2025 with SQL Server 2025.
Iām not sure why SQL 2025 was even mentioned since itās not even GA yet and there will be no new version of SSRS for SQL 2025.
Does anyone know if SQL 2025 and PBIRS will officially be supported for Kinetic 2025.1 when it becomes GA?
Tim just said they are not ready to answer that question yet . . .
Did you happen to try editing an RDL? I know in the past I accidentally installed the Power BI report builder and could not open any of the Epicor SSRS RDLs. With that being said that was a veeeeeeery long time ago.
Alisa, thank you! I must have missed that update while I was composing the post!
I have not yet. I have been trying to find time to set up an Epicor test environment (2025.1) with SQL 2025 and PBIRS. However, the upgrade created a whole bunch of issues with newly introduced bugs, especially in the new way Epicor is processing security for customized layers. It crippled us for a bit until I figured out a band aid. Along with the age-old bug that keeps returning with new versions of Collaborate consuming many extra licenses, we have been busy. I am looking to maybe have a SQL 2025/Epicor 2025.1.6 test setup in about a week.
Yes I downloaded the report builder via the link on the PBIRS server.
Edited the report and reuploaded all with success.
I think he answered without answering.
:ring_bouy: PBIRS it is!
Um⦠no⦠the lack of mentioning a product did not mean I was talking about PBIRS.. in fact, I can say that this was not one of the three candidates we looked at.
the solution is better in our view.
please patiently await our official announcement before proceeding.
Hey, i said no tomatoes, hahaha.
You say that like weāre known for our patience.
The solution is:
JUST WAIT YA IMPATIENT MONKEY!
Eggs and toilet paper are too expensiveā¦
You can actually run SSRS Express + MSSQL Express just fine as a dedicated SSRS server for Epicor. The Epicor DB needs to be on a Standard or Developer instance, but having the ReportServer and reportdata databases on Express works fine.