Did you do the pre-upgrade export, new repository (registered) and import the .al_ files into the new repository?

Kevin:

Yes, performed all of that, and they will push to Excel, but come in with #N/A on every calculation.

Did you do the pre-upgrade export, new repository (registered) and import the .al_ files into the new repository?

Kevin:

Yes, performed all of that, and they will push to Excel, but come in with #N/A on every calculation.

Did you do the pre-upgrade export, new repository (registered) and import the .al_ files into the new repository?

I'm working on this with Machelle and a couple more things - I imported them into my 2025 and they would still not work.  I had to copy over a new Financial report into the folder, then copy tabs from the old to the new and call it a whole new report.  They did not indicate they were Report Designer reports when run after importing.

------------------------------
Beth Bowers
Dog Mom, first and foremost. The rest is all just necessary to keep the dogs in biscuits.
(269) 358-0989
------------------------------


Original Message:
Sent: 08-20-2025 14:40
From: Machelle Adler
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

Kevin:

Yes, performed all of that, and they will push to Excel, but come in with #N/A on every calculation.

------------------------------
Machelle Adler
Consultant
Blytheco LLC


Original Message:
Sent: 08-20-2025 14:07
From: Kevin Moyes
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

Did you do the pre-upgrade export, new repository (registered) and import the .al_ files into the new repository?

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

I'm working on this with Machelle and a couple more things - I imported them into my 2025 and they would still not work.  I had to copy over a new Financial report into the folder, then copy tabs from the old to the new and call it a whole new report.  They did not indicate they were Report Designer reports when run after importing.

Kevin:

Yes, performed all of that, and they will push to Excel, but come in with #N/A on every calculation.

Did you do the pre-upgrade export, new repository (registered) and import the .al_ files into the new repository?

Check your Excel add-ins.  I'm troubleshooting an SI workstation issue / error now, and think the old BI Generator Add-In is interfering on the client system.  This is what my test v2025 system shows, with an SI 8.0 report loaded.  (Presumably, SI Generator is the new BI Generator).

I'm working on this with Machelle and a couple more things - I imported them into my 2025 and they would still not work.  I had to copy over a new Financial report into the folder, then copy tabs from the old to the new and call it a whole new report.  They did not indicate they were Report Designer reports when run after importing.

Kevin:

Yes, performed all of that, and they will push to Excel, but come in with #N/A on every calculation.

Did you do the pre-upgrade export, new repository (registered) and import the .al_ files into the new repository?

I'm not sure if anyone noticed that Sage created a new KB article  -Sage Intelligence Setup and Troubleshooting Guide

It probably doesn't have the answer you're looking for but I found it to be a fairly concise summary of Sage Intelligence setup and there is a section on Sage 100 2025.

C'mon, @Wayne Schulz - you KNOW we depend on you to spoon-feed us any new KB entries.  I like the 2025 summary, but it doesn't seem to apply to this. If it was only happening on the client machine, that would be one thing, but copied over to my machine they work the exact same way. (Exported from older version, imported into my 2025).  Waiting to hear whether it's working for the end user - may have to recreate trees for them.  (Ran into the common issue of Excel not being on the server, so haven't fully tested my "fixed" versions yet.)

I'm not sure if anyone noticed that Sage created a new KB article  -Sage Intelligence Setup and Troubleshooting Guide

It probably doesn't have the answer you're looking for but I found it to be a fairly concise summary of Sage Intelligence setup and there is a section on Sage 100 2025.

Maybe create a new tab and then start copying and pasting a little bit at a time to try and narrow down where it breaks.

C'mon, @Wayne Schulz - you KNOW we depend on you to spoon-feed us any new KB entries.  I like the 2025 summary, but it doesn't seem to apply to this. If it was only happening on the client machine, that would be one thing, but copied over to my machine they work the exact same way. (Exported from older version, imported into my 2025).  Waiting to hear whether it's working for the end user - may have to recreate trees for them.  (Ran into the common issue of Excel not being on the server, so haven't fully tested my "fixed" versions yet.)

I'm not sure if anyone noticed that Sage created a new KB article  -Sage Intelligence Setup and Troubleshooting Guide

It probably doesn't have the answer you're looking for but I found it to be a fairly concise summary of Sage Intelligence setup and there is a section on Sage 100 2025.

Well, in the interest of getting it done, I just copied them all over.  I am assuming they are working (couldn't tell without the trees) because the Task Pane shows up and it didn't on the old copies.  In general, it just does not see those templates as Report Designer Add-In type templates.  Copying over with NO changes seemed to work, but I did try copying back as the same name once and that didn't work, so I changed the name on each of them.  That part could have been my mixup and an unneeded step - I was pretty cranky at that point.

Maybe create a new tab and then start copying and pasting a little bit at a time to try and narrow down where it breaks.

C'mon, @Wayne Schulz - you KNOW we depend on you to spoon-feed us any new KB entries.  I like the 2025 summary, but it doesn't seem to apply to this. If it was only happening on the client machine, that would be one thing, but copied over to my machine they work the exact same way. (Exported from older version, imported into my 2025).  Waiting to hear whether it's working for the end user - may have to recreate trees for them.  (Ran into the common issue of Excel not being on the server, so haven't fully tested my "fixed" versions yet.)

I'm not sure if anyone noticed that Sage created a new KB article  -Sage Intelligence Setup and Troubleshooting Guide

It probably doesn't have the answer you're looking for but I found it to be a fairly concise summary of Sage Intelligence setup and there is a section on Sage 100 2025.

Sage has appeared to create a KB article on this. While the article does not presently ( as of 9/10/25 ) offer any resolutions to this issue it should at least serve as a starting point for anyone experiencing similar issues in the future.

Sage KB -Imported Sage Intelligence Reports don't convert properly to SI version 2025

They're working on a write up of possible work-arounds.

Sage has appeared to create a KB article on this. While the article does not presently ( as of 9/10/25 ) offer any resolutions to this issue it should at least serve as a starting point for anyone experiencing similar issues in the future.

Sage KB -Imported Sage Intelligence Reports don't convert properly to SI version 2025

Work arounds or SOLUTIONS??

They're working on a write up of possible work-arounds.

Sage has appeared to create a KB article on this. While the article does not presently ( as of 9/10/25 ) offer any resolutions to this issue it should at least serve as a starting point for anyone experiencing similar issues in the future.

Sage KB -Imported Sage Intelligence Reports don't convert properly to SI version 2025

Work arounds for now, moving up the chain to press South Africa for solutions

Work arounds or SOLUTIONS??

They're working on a write up of possible work-arounds.

Sage has appeared to create a KB article on this. While the article does not presently ( as of 9/10/25 ) offer any resolutions to this issue it should at least serve as a starting point for anyone experiencing similar issues in the future.

Sage KB -Imported Sage Intelligence Reports don't convert properly to SI version 2025

I've managed to get report working by starting a fresh template and then copying the design from the old template.   However Save Excel template then gives me an error message.

Work arounds for now, moving up the chain to press South Africa for solutions

Work arounds or SOLUTIONS??

They're working on a write up of possible work-arounds.

Sage has appeared to create a KB article on this. While the article does not presently ( as of 9/10/25 ) offer any resolutions to this issue it should at least serve as a starting point for anyone experiencing similar issues in the future.

Sage KB -Imported Sage Intelligence Reports don't convert properly to SI version 2025

I've managed to get report working by starting a fresh template and then copying the design from the old template.   However Save Excel template then gives me an error message.

------------------------------
Thomas Rogers (TomTarget)
Target System Technology, Inc.
------------------------------


Original Message:
Sent: 09-10-2025 16:57
From: Beth Bowers
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

Work arounds for now, moving up the chain to press South Africa for solutions

------------------------------
Beth Bowers
Dog Mom, first and foremost. The rest is all just necessary to keep the dogs in biscuits.
(269) 358-0989


Original Message:
Sent: 09-10-2025 16:41
From: Jeff Schwenk
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

Work arounds or SOLUTIONS??

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!


Original Message:
Sent: 09-10-2025 14:50
From: Beth Bowers
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

They're working on a write up of possible work-arounds.

------------------------------
Beth Bowers
Dog Mom, first and foremost. The rest is all just necessary to keep the dogs in biscuits.
(269) 358-0989


Original Message:
Sent: 09-10-2025 14:47
From: Wayne Schulz
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

Sage has appeared to create a KB article on this. While the article does not presently ( as of 9/10/25 ) offer any resolutions to this issue it should at least serve as a starting point for anyone experiencing similar issues in the future.

Sage KB -Imported Sage Intelligence Reports don't convert properly to SI version 2025

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT

The error 1004 will occur if you have Excel open but is resolved if running Excel 2405 or higher.  I have also received this error if there are issues in the VB scripting after the upgrade.  If you go into the VB scripting and tell it to run through the script, it will halt at the line of code that it has an issue with so you can attempt to resolve the issue.

Error: "Error number 1004, application-defined or object-defined error" on saving SI reports

------------------------------
Machelle Adler
Consultant
Blytheco LLC
------------------------------


Original Message:
Sent: 09-29-2025 17:43
From: Thomas Rogers
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

I've managed to get report working by starting a fresh template and then copying the design from the old template.   However Save Excel template then gives me an error message.

------------------------------
Thomas Rogers (TomTarget)
Target System Technology, Inc.


Original Message:
Sent: 09-10-2025 16:57
From: Beth Bowers
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

Work arounds for now, moving up the chain to press South Africa for solutions

------------------------------
Beth Bowers
Dog Mom, first and foremost. The rest is all just necessary to keep the dogs in biscuits.
(269) 358-0989


Original Message:
Sent: 09-10-2025 16:41
From: Jeff Schwenk
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

Work arounds or SOLUTIONS??

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!


Original Message:
Sent: 09-10-2025 14:50
From: Beth Bowers
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

They're working on a write up of possible work-arounds.

------------------------------
Beth Bowers
Dog Mom, first and foremost. The rest is all just necessary to keep the dogs in biscuits.
(269) 358-0989


Original Message:
Sent: 09-10-2025 14:47
From: Wayne Schulz
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

Sage has appeared to create a KB article on this. While the article does not presently ( as of 9/10/25 ) offer any resolutions to this issue it should at least serve as a starting point for anyone experiencing similar issues in the future.

Sage KB -Imported Sage Intelligence Reports don't convert properly to SI version 2025

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT

I just spoke with Alec at Sage and it seems that developers in South Africa have tracked down the issues on converting reports.

In V2025, you have to setup a new repository, which means that you have to re-register SIR, setup SIR security (if using), copy .tre (trees) to new repository. Most importantly, you have to import/ export out the SIR reports.

For the ones that use the G/L designer addin, they error out after importing when trying to run them (ie missing Add-in). This is due to the version that your imported SIR report was originally written in. If you are still using the original release of the connectors/ subreports,  (ie Accounts 1.0), you need to replace it. Also, the roll up subreport is most likely missing too as it was added later. 

This was a lot easier than copying and pasting sheets into a new report and updating the Excel paths.

Alec is working on updating the new and improve KB on troubleshooting SIR reports to include this. I do have the 1st draft of the steps if anyone wants them instead of waiting on his KB.

Thank you,

Michael

The error 1004 will occur if you have Excel open but is resolved if running Excel 2405 or higher.  I have also received this error if there are issues in the VB scripting after the upgrade.  If you go into the VB scripting and tell it to run through the script, it will halt at the line of code that it has an issue with so you can attempt to resolve the issue.

Error: "Error number 1004, application-defined or object-defined error" on saving SI reports

------------------------------
Machelle Adler
Consultant
Blytheco LLC


Original Message:
Sent: 09-29-2025 17:43
From: Thomas Rogers
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

I've managed to get report working by starting a fresh template and then copying the design from the old template.   However Save Excel template then gives me an error message.

------------------------------
Thomas Rogers (TomTarget)
Target System Technology, Inc.


Original Message:
Sent: 09-10-2025 16:57
From: Beth Bowers
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

Work arounds for now, moving up the chain to press South Africa for solutions

------------------------------
Beth Bowers
Dog Mom, first and foremost. The rest is all just necessary to keep the dogs in biscuits.
(269) 358-0989


Original Message:
Sent: 09-10-2025 16:41
From: Jeff Schwenk
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

Work arounds or SOLUTIONS??

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!


Original Message:
Sent: 09-10-2025 14:50
From: Beth Bowers
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

They're working on a write up of possible work-arounds.

------------------------------
Beth Bowers
Dog Mom, first and foremost. The rest is all just necessary to keep the dogs in biscuits.
(269) 358-0989


Original Message:
Sent: 09-10-2025 14:47
From: Wayne Schulz
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

Sage has appeared to create a KB article on this. While the article does not presently ( as of 9/10/25 ) offer any resolutions to this issue it should at least serve as a starting point for anyone experiencing similar issues in the future.

Sage KB -Imported Sage Intelligence Reports don't convert properly to SI version 2025

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT

@Michael Davis - I would genuinely love to get your first draft. Thank you for sharing your convo with Alec. I've been holding off doing upgrades until this issue has a solution.

Karen

I just spoke with Alec at Sage and it seems that developers in South Africa have tracked down the issues on converting reports.

In V2025, you have to setup a new repository, which means that you have to re-register SIR, setup SIR security (if using), copy .tre (trees) to new repository. Most importantly, you have to import/ export out the SIR reports.

For the ones that use the G/L designer addin, they error out after importing when trying to run them (ie missing Add-in). This is due to the version that your imported SIR report was originally written in. If you are still using the original release of the connectors/ subreports,  (ie Accounts 1.0), you need to replace it. Also, the roll up subreport is most likely missing too as it was added later. 

This was a lot easier than copying and pasting sheets into a new report and updating the Excel paths.

Alec is working on updating the new and improve KB on troubleshooting SIR reports to include this. I do have the 1st draft of the steps if anyone wants them instead of waiting on his KB.

Thank you,

Michael

The error 1004 will occur if you have Excel open but is resolved if running Excel 2405 or higher.  I have also received this error if there are issues in the VB scripting after the upgrade.  If you go into the VB scripting and tell it to run through the script, it will halt at the line of code that it has an issue with so you can attempt to resolve the issue.

Error: "Error number 1004, application-defined or object-defined error" on saving SI reports

------------------------------
Machelle Adler
Consultant
Blytheco LLC


Original Message:
Sent: 09-29-2025 17:43
From: Thomas Rogers
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

I've managed to get report working by starting a fresh template and then copying the design from the old template.   However Save Excel template then gives me an error message.

------------------------------
Thomas Rogers (TomTarget)
Target System Technology, Inc.


Original Message:
Sent: 09-10-2025 16:57
From: Beth Bowers
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

Work arounds for now, moving up the chain to press South Africa for solutions

------------------------------
Beth Bowers
Dog Mom, first and foremost. The rest is all just necessary to keep the dogs in biscuits.
(269) 358-0989


Original Message:
Sent: 09-10-2025 16:41
From: Jeff Schwenk
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

Work arounds or SOLUTIONS??

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!


Original Message:
Sent: 09-10-2025 14:50
From: Beth Bowers
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

They're working on a write up of possible work-arounds.

------------------------------
Beth Bowers
Dog Mom, first and foremost. The rest is all just necessary to keep the dogs in biscuits.
(269) 358-0989


Original Message:
Sent: 09-10-2025 14:47
From: Wayne Schulz
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

Sage has appeared to create a KB article on this. While the article does not presently ( as of 9/10/25 ) offer any resolutions to this issue it should at least serve as a starting point for anyone experiencing similar issues in the future.

Sage KB -Imported Sage Intelligence Reports don't convert properly to SI version 2025

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT

@Michael Davis - I would genuinely love to get your first draft. Thank you for sharing your convo with Alec. I've been holding off doing upgrades until this issue has a solution.

Karen

I just spoke with Alec at Sage and it seems that developers in South Africa have tracked down the issues on converting reports.

In V2025, you have to setup a new repository, which means that you have to re-register SIR, setup SIR security (if using), copy .tre (trees) to new repository. Most importantly, you have to import/ export out the SIR reports.

For the ones that use the G/L designer addin, they error out after importing when trying to run them (ie missing Add-in). This is due to the version that your imported SIR report was originally written in. If you are still using the original release of the connectors/ subreports,  (ie Accounts 1.0), you need to replace it. Also, the roll up subreport is most likely missing too as it was added later. 

This was a lot easier than copying and pasting sheets into a new report and updating the Excel paths.

Alec is working on updating the new and improve KB on troubleshooting SIR reports to include this. I do have the 1st draft of the steps if anyone wants them instead of waiting on his KB.

Thank you,

Michael

The error 1004 will occur if you have Excel open but is resolved if running Excel 2405 or higher.  I have also received this error if there are issues in the VB scripting after the upgrade.  If you go into the VB scripting and tell it to run through the script, it will halt at the line of code that it has an issue with so you can attempt to resolve the issue.

Error: "Error number 1004, application-defined or object-defined error" on saving SI reports

------------------------------
Machelle Adler
Consultant
Blytheco LLC


Original Message:
Sent: 09-29-2025 17:43
From: Thomas Rogers
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

I've managed to get report working by starting a fresh template and then copying the design from the old template.   However Save Excel template then gives me an error message.

------------------------------
Thomas Rogers (TomTarget)
Target System Technology, Inc.


Original Message:
Sent: 09-10-2025 16:57
From: Beth Bowers
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

Work arounds for now, moving up the chain to press South Africa for solutions

------------------------------
Beth Bowers
Dog Mom, first and foremost. The rest is all just necessary to keep the dogs in biscuits.
(269) 358-0989


Original Message:
Sent: 09-10-2025 16:41
From: Jeff Schwenk
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

Work arounds or SOLUTIONS??

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!


Original Message:
Sent: 09-10-2025 14:50
From: Beth Bowers
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

They're working on a write up of possible work-arounds.

------------------------------
Beth Bowers
Dog Mom, first and foremost. The rest is all just necessary to keep the dogs in biscuits.
(269) 358-0989


Original Message:
Sent: 09-10-2025 14:47
From: Wayne Schulz
Subject: Sage 100 v2025 Sage Intelligence Conversion Issues

Sage has appeared to create a KB article on this. While the article does not presently ( as of 9/10/25 ) offer any resolutions to this issue it should at least serve as a starting point for anyone experiencing similar issues in the future.

Sage KB -Imported Sage Intelligence Reports don't convert properly to SI version 2025

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT

10-8-2025 - Sage has an updated knowledge article here -Imported Sage Intelligence Reports don't convert properly to SI version 2025 and higher