MS Office Click-to-Run deployments do not appear to be fully supported by Sage 300 2014. No notes on support in 2016. Support team did not know what this was initially, then stated not tested.

Specifically, issue present in PJC when attempting import of xls or xlsx - error comes back with module not found error.

Tested with Office 2016 and 2013 ProPlus 32 bit. Both deployed as MS Click-to-Run, and licenced through Office 365.

A note before Sage says that Click-to-Run is a fringe need: This has been around since Office 2010, and is the exclusive way that Office 365 deployments are licenced. Since Mid 2015 it has also been supported on terminal servers. This is MS' direction forward, and major vendors such as Sage should fully support this.

Our workaround was to purchase a "traditional" licence of Office, which can be deployed via MSI - and worked immediately with Sage. This is an additional cost, different update structure, different update GPO, and for software we are already fully licenced for and working with.

Sage support was not helpful in resolving this. Sage should fully support Click-to-Run deployed Office installs.

by: Colin P. | over a year ago | Setup / Environment