Sage 100

During MOTM 2025 I thought Sage said the Sage Intelligence updates was all under-the-hood type stuff with no new functionality.

Sage KB related to SI upgrades indicates you will need a new repository for the new SI version.

During MOTM 2025 I thought Sage said the Sage Intelligence updates was all under-the-hood type stuff with no new functionality.

That KB is only three years old.  Exporting/Importing is a ROYAL pita.  I had hoped things might be different.  Big Sigh!

Sage KB related to SI upgrades indicates you will need a new repository for the new SI version.

During MOTM 2025 I thought Sage said the Sage Intelligence updates was all under-the-hood type stuff with no new functionality.

I installed v2025 standard and went into Sage Intelligence for the 1st time and the report repository defaulted to my report repository I have set on all my other Sage installs on my laptop. It never asked where the repository path was like on previous Sage versions.

That KB is only three years old.  Exporting/Importing is a ROYAL pita.  I had hoped things might be different.  Big Sigh!

Sage KB related to SI upgrades indicates you will need a new repository for the new SI version.

During MOTM 2025 I thought Sage said the Sage Intelligence updates was all under-the-hood type stuff with no new functionality.

Good to know, @Dana Halpin! I was going to say that I would be surprised if we had to go back to doing "create new folder/export from old version/import to new version". That is a BIG PITA. 

I installed v2025 standard and went into Sage Intelligence for the 1st time and the report repository defaulted to my report repository I have set on all my other Sage installs on my laptop. It never asked where the repository path was like on previous Sage versions.

That KB is only three years old.  Exporting/Importing is a ROYAL pita.  I had hoped things might be different.  Big Sigh!

Sage KB related to SI upgrades indicates you will need a new repository for the new SI version.

During MOTM 2025 I thought Sage said the Sage Intelligence updates was all under-the-hood type stuff with no new functionality.

Here is the information I have as of 3/13 re: SI for Sage 100:

• SI 8.0 in Sage 100 v2025 – changes mainly in backend
• Coming soon: Sage business reporting* – apparently a huge first, worldwide exclusive.  Not sure how this compares to SI, or actually it may just be enhancement to SI.  This might be Infisio?/invisio? - sage acquired 6mo ago.  Incl intention to make SI more 'open' and be able to pull data from other systems
• *  this appears to be a new set of excel-based, real-time reporting capabilities, likely Infineo which I guess was acquired by Sage France last year.

Good to know, @Dana Halpin! I was going to say that I would be surprised if we had to go back to doing "create new folder/export from old version/import to new version". That is a BIG PITA. 

I installed v2025 standard and went into Sage Intelligence for the 1st time and the report repository defaulted to my report repository I have set on all my other Sage installs on my laptop. It never asked where the repository path was like on previous Sage versions.

That KB is only three years old.  Exporting/Importing is a ROYAL pita.  I had hoped things might be different.  Big Sigh!

Sage KB related to SI upgrades indicates you will need a new repository for the new SI version.

During MOTM 2025 I thought Sage said the Sage Intelligence updates was all under-the-hood type stuff with no new functionality.

Sage KB related to SI upgrades indicates you will need a new repository for the new SI version.

During MOTM 2025 I thought Sage said the Sage Intelligence updates was all under-the-hood type stuff with no new functionality.

Here is a note on our first foray into 2025 using client data:

We did a test upgrade to version 2025 for a client that is just using GL and Accounts Payable modules. They are vanilla and on version 2015. The Upgrade checklist for 2025 only lists upgrading from version 2019 and newer, but being the daredevils we are, we decided to see what would happen if we tried going directly from their 2015 version. During the migration process, we got an error message (attached). Prepare failed .... Failed to create table SY_OfficeUserMap: Dictionary not found.  We went back and upgraded from 2015 to version 2020 and then upgraded from 2020 to 2025 and everything went just fine. 

------------------------------
David Overholt
Programmer/Project Manager
DWD Technology Group
Fort Wayne IN
(260) 399-8655
------------------------------

Conversion issue or v2025 issue.

Attempted to open SO entry in one of my companies in v2025.  Error below encountered.  SO works fine in other companies.  I copied that company's MASXXX from v2024 and reconverted it.  No improvement.  Not much in the KB.

All musings are appreciated.

Thanks in advance.

Here is a note on our first foray into 2025 using client data:

We did a test upgrade to version 2025 for a client that is just using GL and Accounts Payable modules. They are vanilla and on version 2015. The Upgrade checklist for 2025 only lists upgrading from version 2019 and newer, but being the daredevils we are, we decided to see what would happen if we tried going directly from their 2015 version. During the migration process, we got an error message (attached). Prepare failed .... Failed to create table SY_OfficeUserMap: Dictionary not found.  We went back and upgraded from 2015 to version 2020 and then upgraded from 2020 to 2025 and everything went just fine. 

------------------------------
David Overholt
Programmer/Project Manager
DWD Technology Group
Fort Wayne IN
(260) 399-8655

Try rebuilding IM and SO key files.  See the link below

https://communityhub.sage.com/us/sage100/f/distribution-manufacturing-and-internet-modules/35302/program-entered-cannot-be-found

Conversion issue or v2025 issue.

Attempted to open SO entry in one of my companies in v2025.  Error below encountered.  SO works fine in other companies.  I copied that company's MASXXX from v2024 and reconverted it.  No improvement.  Not much in the KB.

All musings are appreciated.

Thanks in advance.

Here is a note on our first foray into 2025 using client data:

We did a test upgrade to version 2025 for a client that is just using GL and Accounts Payable modules. They are vanilla and on version 2015. The Upgrade checklist for 2025 only lists upgrading from version 2019 and newer, but being the daredevils we are, we decided to see what would happen if we tried going directly from their 2015 version. During the migration process, we got an error message (attached). Prepare failed .... Failed to create table SY_OfficeUserMap: Dictionary not found.  We went back and upgraded from 2015 to version 2020 and then upgraded from 2020 to 2025 and everything went just fine. 

------------------------------
David Overholt
Programmer/Project Manager
DWD Technology Group
Fort Wayne IN
(260) 399-8655

Doug,

It is Saturday night.  Aren't the Cubbies playing??

Thanks for the outreach.  I activated the IM module and the problem disappeared.

Try rebuilding IM and SO key files.  See the link below

https://communityhub.sage.com/us/sage100/f/distribution-manufacturing-and-internet-modules/35302/program-entered-cannot-be-found

Conversion issue or v2025 issue.

Attempted to open SO entry in one of my companies in v2025.  Error below encountered.  SO works fine in other companies.  I copied that company's MASXXX from v2024 and reconverted it.  No improvement.  Not much in the KB.

All musings are appreciated.

Thanks in advance.

Here is a note on our first foray into 2025 using client data:

We did a test upgrade to version 2025 for a client that is just using GL and Accounts Payable modules. They are vanilla and on version 2015. The Upgrade checklist for 2025 only lists upgrading from version 2019 and newer, but being the daredevils we are, we decided to see what would happen if we tried going directly from their 2015 version. During the migration process, we got an error message (attached). Prepare failed .... Failed to create table SY_OfficeUserMap: Dictionary not found.  We went back and upgraded from 2015 to version 2020 and then upgraded from 2020 to 2025 and everything went just fine. 

------------------------------
David Overholt
Programmer/Project Manager
DWD Technology Group
Fort Wayne IN
(260) 399-8655

Cubs beat the Brewers today.  Unfortunately I have a bad cold so trying to rest and wait it out 

Doug,

It is Saturday night.  Aren't the Cubbies playing??

Thanks for the outreach.  I activated the IM module and the problem disappeared.

Try rebuilding IM and SO key files.  See the link below

https://communityhub.sage.com/us/sage100/f/distribution-manufacturing-and-internet-modules/35302/program-entered-cannot-be-found

Conversion issue or v2025 issue.

Attempted to open SO entry in one of my companies in v2025.  Error below encountered.  SO works fine in other companies.  I copied that company's MASXXX from v2024 and reconverted it.  No improvement.  Not much in the KB.

All musings are appreciated.

Thanks in advance.

Here is a note on our first foray into 2025 using client data:

We did a test upgrade to version 2025 for a client that is just using GL and Accounts Payable modules. They are vanilla and on version 2015. The Upgrade checklist for 2025 only lists upgrading from version 2019 and newer, but being the daredevils we are, we decided to see what would happen if we tried going directly from their 2015 version. During the migration process, we got an error message (attached). Prepare failed .... Failed to create table SY_OfficeUserMap: Dictionary not found.  We went back and upgraded from 2015 to version 2020 and then upgraded from 2020 to 2025 and everything went just fine. 

------------------------------
David Overholt
Programmer/Project Manager
DWD Technology Group
Fort Wayne IN
(260) 399-8655

This started popping up when exiting Excel AFTER I installed the v2025 client on a WIN 11 workstation.  Office 2019 is installed on the workstation.

Nothing was found on KB (not surprising based on my search skills).

New add ins are installed (second screenshot) below.

Not critical yet, more of a heads up wondering if others have encountered it.

Cubs beat the Brewers today.  Unfortunately I have a bad cold so trying to rest and wait it out 

Doug,

It is Saturday night.  Aren't the Cubbies playing??

Thanks for the outreach.  I activated the IM module and the problem disappeared.

Try rebuilding IM and SO key files.  See the link below

https://communityhub.sage.com/us/sage100/f/distribution-manufacturing-and-internet-modules/35302/program-entered-cannot-be-found

Conversion issue or v2025 issue.

Attempted to open SO entry in one of my companies in v2025.  Error below encountered.  SO works fine in other companies.  I copied that company's MASXXX from v2024 and reconverted it.  No improvement.  Not much in the KB.

All musings are appreciated.

Thanks in advance.

Here is a note on our first foray into 2025 using client data:

We did a test upgrade to version 2025 for a client that is just using GL and Accounts Payable modules. They are vanilla and on version 2015. The Upgrade checklist for 2025 only lists upgrading from version 2019 and newer, but being the daredevils we are, we decided to see what would happen if we tried going directly from their 2015 version. During the migration process, we got an error message (attached). Prepare failed .... Failed to create table SY_OfficeUserMap: Dictionary not found.  We went back and upgraded from 2015 to version 2020 and then upgraded from 2020 to 2025 and everything went just fine. 

------------------------------
David Overholt
Programmer/Project Manager
DWD Technology Group
Fort Wayne IN
(260) 399-8655

I haven't tried this yet, but just wondering.  If you install v2025 on a workstation running v2024, is the SI 2.0 backwards compatible to 2024.  In other words, can I run v2024 SI reports using the SI 2.0?

Asking for another friend (I have several believe it or not)

TIA

This started popping up when exiting Excel AFTER I installed the v2025 client on a WIN 11 workstation.  Office 2019 is installed on the workstation.

Nothing was found on KB (not surprising based on my search skills).

New add ins are installed (second screenshot) below.

Not critical yet, more of a heads up wondering if others have encountered it.

Cubs beat the Brewers today.  Unfortunately I have a bad cold so trying to rest and wait it out 

Doug,

It is Saturday night.  Aren't the Cubbies playing??

Thanks for the outreach.  I activated the IM module and the problem disappeared.

Try rebuilding IM and SO key files.  See the link below

https://communityhub.sage.com/us/sage100/f/distribution-manufacturing-and-internet-modules/35302/program-entered-cannot-be-found

Conversion issue or v2025 issue.

Attempted to open SO entry in one of my companies in v2025.  Error below encountered.  SO works fine in other companies.  I copied that company's MASXXX from v2024 and reconverted it.  No improvement.  Not much in the KB.

All musings are appreciated.

Thanks in advance.

Here is a note on our first foray into 2025 using client data:

We did a test upgrade to version 2025 for a client that is just using GL and Accounts Payable modules. They are vanilla and on version 2015. The Upgrade checklist for 2025 only lists upgrading from version 2019 and newer, but being the daredevils we are, we decided to see what would happen if we tried going directly from their 2015 version. During the migration process, we got an error message (attached). Prepare failed .... Failed to create table SY_OfficeUserMap: Dictionary not found.  We went back and upgraded from 2015 to version 2020 and then upgraded from 2020 to 2025 and everything went just fine. 

------------------------------
David Overholt
Programmer/Project Manager
DWD Technology Group
Fort Wayne IN
(260) 399-8655

Who has already proceeded with v2025 Upgrades including SI (Sage Intelligence)?  It sounds like @Beth Bowers had to perform the extra steps but @Dana Halpin did not, so how is everyone else faring?

I haven't tried this yet, but just wondering.  If you install v2025 on a workstation running v2024, is the SI 2.0 backwards compatible to 2024.  In other words, can I run v2024 SI reports using the SI 2.0?

Asking for another friend (I have several believe it or not)

TIA

This started popping up when exiting Excel AFTER I installed the v2025 client on a WIN 11 workstation.  Office 2019 is installed on the workstation.

Nothing was found on KB (not surprising based on my search skills).

New add ins are installed (second screenshot) below.

Not critical yet, more of a heads up wondering if others have encountered it.

Cubs beat the Brewers today.  Unfortunately I have a bad cold so trying to rest and wait it out 

Doug,

It is Saturday night.  Aren't the Cubbies playing??

Thanks for the outreach.  I activated the IM module and the problem disappeared.

Try rebuilding IM and SO key files.  See the link below

https://communityhub.sage.com/us/sage100/f/distribution-manufacturing-and-internet-modules/35302/program-entered-cannot-be-found

Conversion issue or v2025 issue.

Attempted to open SO entry in one of my companies in v2025.  Error below encountered.  SO works fine in other companies.  I copied that company's MASXXX from v2024 and reconverted it.  No improvement.  Not much in the KB.

All musings are appreciated.

Thanks in advance.

Here is a note on our first foray into 2025 using client data:

We did a test upgrade to version 2025 for a client that is just using GL and Accounts Payable modules. They are vanilla and on version 2015. The Upgrade checklist for 2025 only lists upgrading from version 2019 and newer, but being the daredevils we are, we decided to see what would happen if we tried going directly from their 2015 version. During the migration process, we got an error message (attached). Prepare failed .... Failed to create table SY_OfficeUserMap: Dictionary not found.  We went back and upgraded from 2015 to version 2020 and then upgraded from 2020 to 2025 and everything went just fine. 

------------------------------
David Overholt
Programmer/Project Manager
DWD Technology Group
Fort Wayne IN
(260) 399-8655