fuzed Posted February 7, 2018 Report Share Posted February 7, 2018 Guys, I have an old Intella 1.7.3 case which I use to train users on, this is some old enron data, I was going to reuse but can't load in 2.1, is there any way around this or will I have to create a new case? Quote Link to comment Share on other sites More sharing options...
ŁukaszBachman Posted February 19, 2018 Report Share Posted February 19, 2018 Hi fuzed, You'll need to create a new case. 1.7.3 is really old so it's best if you would train your users with most up to date version. Quote Link to comment Share on other sites More sharing options...
fuzed Posted February 21, 2018 Author Report Share Posted February 21, 2018 Yes I did that in the end, however if I have an old case file that a user needs to come back to later on how can I get this done? We have some old cases that are no longer being accessed, but I'm sure someone in the future may ask to access that case file?I think backwards compatibility is important, or there should be a means to port over user data from an old case into a new case? Quote Link to comment Share on other sites More sharing options...
AdamS Posted February 22, 2018 Report Share Posted February 22, 2018 Fuzed I've come across this with some government contract work that I do from time to time. The easiest solution is to install 1.7.x and use that to view the data. You can have different versions of Intella running side by side without any issues. Alternatively you may be able to upgrade the case in steps, a little time consuming but install multiple versions of intella on the machine (1.7, 1.8, 1.9 ect) then upgrade the case one version at a time until it's up to current. Not sure if that's possible but it might be an alternative work around. Quote Link to comment Share on other sites More sharing options...
ŁukaszBachman Posted February 27, 2018 Report Share Posted February 27, 2018 Having 1.7.x installed for such cases is a good idea. Keep in mind that this version was released 5 years ago, which translates to 5 years of ongoing improvements and modifications of our databases. This makes migration path between major versions complex, so if you want to be on a safe side it's best to open a case in version where it was created (unless you badly need a feature from more recent release). This of course doesn't mean that we don't provide backwards compatibility layer. We pay very close attention to that matter and we never leave our users without clear instructions how to proceed. Each time we issue a new release we also publish "Release notes" document. The last section is always about case migration and backwards compatibility, so please get familiar with those instructions if you want to be pro-active about supporting old cases. Quote Link to comment Share on other sites More sharing options...
fuzed Posted February 27, 2018 Author Report Share Posted February 27, 2018 Its no good as the clients require access remotely i.e. via Intella Connect, will look at the instructions. Quote Link to comment Share on other sites More sharing options...
fuzed Posted March 14, 2018 Author Report Share Posted March 14, 2018 Thanks AdamS, all sorted, used your suggestion and was able to upgrade the case using that, and now hosted and being checked by the client! 1 Quote Link to comment Share on other sites More sharing options...
ŁukaszBachman Posted March 22, 2018 Report Share Posted March 22, 2018 Very happy to hear that! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.