Sage 100

Sage Intelligence installed with version 5.2. Any ideas on why there would be two ODBC drivers pulling into the Tenant Cache (causing duplicate company data and corresponding errors)? I have cleared the tenant cache completely and they still come back after users log in and run reports. Users are logging into an RDP session to access Sage. Sage Premium has never been installed, and there is only one ODBC driver listed in the User DSN, & no System DSN's exist. Tried following the info in KB Article 63230, the last step says to uninstall and reinstall. But the client wants to make sure there isn't another option (regedit maybe?) as the reinstall is pretty invasive on their operations. Anyone seen this before?

Duplicating GL or other data? I just reported an issue to SI regarding row sets for consolidated financials showing duplicate rows. They confirmed that layout designer row set has a bug.

I've seen this and while I believe it was a local install, it was specific to when 1 person logged in. Is there another software that is installed and a user in the RDP session uses? Never did figure out what the problem was and how to resolve it other than to clear the cache.

@MoiraGoggin it is duplicating the Account tab. The company in question is listing all GL Accounts twice (Spreadsheet attached first ref lines 14350 and first repeater on 16000), do you know if there is a KB Article on it yet? @NancyHanson This appears to be coming from multiple users, but they are all logging into the Same RDP session, I will check for other installs that might be lingering.

@MichelleForsey I don't expect there is a KB yet, it was just confirmed to be an issue in the last couple of days. In my case it occured when using the Layout Generator with a row set. Even though the company code was specific in the layout, the account would repeat for every occurance of that account in the consolidated company code list. The data was only for the company code specified in the layout. So the account would repeat but have the same amount The suggested work around was to use the task pane formula, i.e., GLActual etc.