go to post Colin Brough · May 18, 2023 For completeness / in case others come across this, turned out the XML export file was being corrupted during transfer between the two systems. It was a CR/LF corruption - in our specific case CR/LF was getting converted to CR/CR/LF !!Highlighted that DTL's specifically appear sensitive to CR/LF changes - we've subsequently come across the same #6301 error loading DTL's get CR/LF modified in another way (we're still tracking that one down, though suspicion currently is with git...)
go to post Colin Brough · Apr 21, 2023 Thanks @Evgeny Shvarov. Unfortunately can't use Iris yet - maybe at some point in the future - but a useful extra benefit when we do make the transition.
go to post Colin Brough · Apr 20, 2023 Thanks Cristiano. I'd found the page you linked to before, but its not very explicit about uninstallation! Would I be correct in interpreting it as: only uninstall option is the unattended section at https://docs.intersystems.com/ens201817/csp/docbook/DocBook.UI.Page.cls?... would I be correct to interpret 'CacheC' in the example command as the instance name of the Ensemble installation to be uninstalled? Or is that the folder name on the filesystem where it is in installed? Not familiar with Windows Registry editing, so can I safely delete those two trees in the registry if i want a completely fresh start? Thanks!
go to post Colin Brough · Feb 20, 2023 Thanks all for responding. Really only adding this message so I can try and mark the question as answered - since there are the two approaches (ompare and using git/repo tools), not wanting to mark one or other as the answer, since both have merits and may be helpful for different situations. I suspect we'll try the git/repo tools approach first, given our particular mix of platform and experience.
go to post Colin Brough · Feb 16, 2023 Thanks for suggestions so far.One challenge is our organisation is very wary of installing any additional code (as Alex suggested) or hooking up something like VS Code, to the live server, which is passing patient information between the various hospital systems... The test system has a little more flexibility, but organisation is a bit twitchy!! Would a plausible path be to sort of follow Eduard's suggestion, but: Export code from live (an export of the classes via Management portal, or if better an export via Studio) to XML Export code from test (as above) to XML On a local laptop, import live code to a newly created namespace and commit from there to a GitLab repo On same local laptop, import test code and commit from there to the GitLab repo Compare as suggested....
