Sage 100

SI Gurus: In upgrading from 2015 to 2018 I see the existing reports have the Rollups Union SubReport, so is there any reason to export the existing reports, create the new repository, license SI and then import the reports? I've always done that but my customer is really balking about the process, time, etc. to do this - he has 60 reports. What are you all doing with these upgrades - just using the same repository or doing the Sage Way and export/import?

I no longer do that - maybe 2014 was the last time?

Do you just use a generic Repository Name then? I've always done SI..._2016, etc. Any idea why Sage would still want us to export/import (per the upgrade guide)? Is there anything new in v2018 of SI?

I believe 2015 was the last SI update. I also used to create a folder based on the year, but after 2016 I have just left it place.

I do generic repositories, just like for Paperless, ACH, etc.

I do export them (just in case and because it's in Sage's instructions), but use the same repository, since that seems to work fine. From now on, I'll be making generically named repositories.

It is my experience you only need to make a new BI_Repository if the version of SI or the version of the Designer Add-In has been upgraded. If it has you can use the bulk export/import tool on the tool bar which is faster than doing 1 by 1. If it hasn't I just point the new workstation after the upgrade to the old BI_Repository and it seems to work fine even though Sage says not to do that.

Thanks everyone, just an FYI, Sage SI Guru (who shall remain nameless!) mentioned there would be no more enhancements to the 'Desktop/Local' version of SI, rather they are concentrating on a Cloud/Web Version (hesitant to say Cloud given Sage's idea of Cloud!!). He claimed he knew nothing else about it so that's all I know too. Doesn't that get you thinking about how it might work and any enhancements that might be put into it?