Sage 100

I have a Sage Intelligence issue. I am trying to consolidate 2 companies data for a financial report. Under the Report Designer Add-In Consolidation menu, I have added the company codes to each of the sub-reports. Then, when I run the Consolidated report, I receive the message ""This workbook does not have valid data to use in the Report Designer Add-In"". I checked and the same codes are included in all the sub-reports. I am still holding with Sage and after 30 minutes so far, I am sure I am either in the wrong queue or they won't help with Intelligence issues. Any help would be greatly appreciated. TIA.

check permissions on Program Filesx86\common files\bi* folders, also if first time using SI on this machine, uninstall wksetup, install again making sure UAC is turned off. if you do this, you need to fix permissions again.

Checked permissions just to confirm. All other reports work fine, it's just the consolidated reports.

I believe you need the Connector license in order to do any sort of consolidations.

I thought the license might be the case, but I have a Connector license. So, I tried it on my laptop that only has Sage 2017 and 2018 on it, no earlier versions, and the consolidation works. The only consolidation option is the menu item labeled ""Consolidation Report Designer"". On my desktop computer, I have versions of Sage going back to 2015 and on my 2017 version, I don't have the menu item above, instead I have ""Report Designer Add-In Consolidation"". It must be something on my desktop PC. I wonder if I should reinstall the Add-In from years ago.

I agree about the connector license being needed. For SBI, do you need to check ""Allow external access"" in LM?

@JaneCavanaugh I ws working on SI a few months ago trying to help a client with the designer add-in and saw the same thing you did. Documentation and my current installs do not have the same folder verbiage. I think they changed it, don't think uninstalling will make a difference.

I should remember to always try the simple things first. Reinstalled workstation setup and that seem to have fixed the issue. I have multiple versions of Sage 100 installed on my computer so something got confused (not me of course).