go to post Ben Spead · Dec 15 P.S. Similar to how you could feed "test" into the D.C. search with the following URL: https://community.intersystems.com/smartsearch?search=test
go to post Ben Spead · Dec 11 @Subtropical.Bob - I suggest you reach out the InterSystems Support and they can help you sort this out.
go to post Ben Spead · Dec 3 agreed!! the Kindle is an awesome option. I use mine pretty much daily :)
go to post Ben Spead · Nov 20 Does it fail in any browser other than Edge? I can't get Edge to fail (nor Chrome not Chrome incognito). Just trying to figure out what might be different for you.
go to post Ben Spead · Nov 20 @Scott Roth - what browser are you using? Can you try in an incognito browser to bypass any cookies or settings which could be impacting behavior? (I am not able to replicate your results)
go to post Ben Spead · Nov 20 There is no rollback mechanism built into the installer (unless there is an issue in the middle of the installation in which case it will back out the installation). If you are using a VM the best practice is to snapshot your VM prior to upgrade and roll back to the snapshot if something goes wrong. This should be done with care because any data changed post upgrade will be lost when you restore the snapshot.
go to post Ben Spead · Nov 1 @Yuhong Snyder - the following should be helpful to you: https://github.com/intersystems/git-source-control/tree/main/docs https://community.intersystems.com/post/video-git-gitlab-shared-development-environments (also the article prior and following) https://community.intersystems.com/post/git-source-control-launches-release-240-new-basic-mode Also, in the future we plan to create a new #EmbeddedGit tag to make it easier to follow news and Q&A for these tools
go to post Ben Spead · Oct 28 @Scott Roth - are you sure that you re-exported the source after /exportversion was set in the system exporting the code that would be imported into 2022.1? If you are certain of this, then please reach out to Support because I am not sure why that would not work
go to post Ben Spead · Oct 28 @Scott Roth - best practice in cases like this is to set the /exportversion qualifier in the DEV environment (or whatever is exporting the source) until all of your pipeline is on the newer version. E.g. w $system.OBJ.SetQualifiers("/exportversion=iris2022.1") This should prevent any newer attributes from being included in the exported XML which would prevent import on an earlier version. ref: https://docs.intersystems.com/iris20242/csp/docbook/Doc.View.cls?KEY=RCOS_vsystem_flags_qualifiers
go to post Ben Spead · Oct 22 Yes indeed! It was a great new challenge for me to reach new personal records on my walkstation :)
go to post Ben Spead · Oct 22 Terrific and major enhancement! Thank you all who contributed! Looking forward to hearing feedback as this starts getting traction in the field.
go to post Ben Spead · Oct 17 you will need to discuss with your IT administrators and get it categorized appropriately within your organization
go to post Ben Spead · Oct 11 @Timothy Leavitt - great work on continuing to move this critical piece of our tech ecosystem forward!!
