go to post John Murray · Jan 5, 2023 Apparently something was messed up at my end. I deleted and re-fetched the container and now all is good.
go to post John Murray · Jan 5, 2023 Maybe I did something wrong, but when I start a container from containers.intersystems.com/intersystems/iris-community:2022.3.0.570.0 I get an IRIS whose $ZV reports 2022.3.0.555.0
go to post John Murray · Jan 1, 2023 https://community.intersystems.com/post/how-recover-management-portal-sy... is a place to start.
go to post John Murray · Dec 20, 2022 Routines and classes created and edited in Studio are stored within the InterSystems database associated with the namespace Studio connected to.
go to post John Murray · Dec 16, 2022 If you'd like to add your vote to getting InterSystems to publish on npm the package that adopters need, please consider doing that at https://ideas.intersystems.com/ideas/DPI-I-326
go to post John Murray · Dec 12, 2022 Perhaps worth noting that you can combine Joel's "#dim" and "set" lines into a single one if you wish. See https://docs.intersystems.com/iris20222/csp/docbook/DocBook.UI.Page.cls?...
go to post John Murray · Dec 9, 2022 you map the affected Namespace using ECP to the newer version and use VSCode Beware - Plenty of pitfalls waiting for you if you use a later version environment to edit code stored in a remote database hosted on an earlier version.
go to post John Murray · Dec 7, 2022 Do things improve if you rewrite your first line to be this? #dim tObservation as HS.SDA3.Observation = ##class(HS.SDA3.Observation).%New()
go to post John Murray · Dec 5, 2022 I suggest you use InterSystems Portal, go to System Operation section, then Databases. Look at which databases lie within the mountpoint which is showing 81% use:
go to post John Murray · Nov 18, 2022 Besides the above, I also noticed that the parser also fails when calling a %SYS routine as in: do DecomposeStatus^%apiOBJ(sc,.err,"-d") @Victor Gordillo please clarify what you mean by "the parser fails". Maybe with a screenshot? InterSystems deletes the source code of many %-routines before shipping, including %apiOBJ. Perhaps this is causing the problem you are seeing.
go to post John Murray · Nov 11, 2022 Previously raised at https://github.com/intersystems/language-server/issues/77 and in several other issues that were marked as duplicates of this.
go to post John Murray · Nov 9, 2022 Good to see this. Minor nit is the Info panel at https://openexchange.intersystems.com/package/ObjectScript-Package-Manager still has some links pointing to the old intersystems-community repo. They forward correctly but deserve to be updated anyway.
go to post John Murray · Oct 27, 2022 This was fixed by me on https://github.com/intersystems-community/webterminal/pull/149 in July 2022. The ZPM package is outdated. I recommend you use instructions at https://intersystems-community.github.io/webterminal/#docs to install the latest version.
go to post John Murray · Oct 26, 2022 @Benjamin De Boe on WRC #956754 (2021.1) we reported that the InterSystems UDL export and load utilities ignore the /exportselectivity and /importselectivity qualifiers. We were told this is intentional and no changes were planned. Did this change? Are they now supported? If so, from which version onwards?
go to post John Murray · Oct 24, 2022 Does https://intersystems-community.github.io/vscode-objectscript/configurati... help you?
go to post John Murray · Oct 21, 2022 In the Extensions view if you search for "intersystems" does it offer you the option of installing the extensions into your container? Or have you already done that?
go to post John Murray · Oct 21, 2022 Probably our biggest pain point related to InterSystems software upgrade, and one we have to try and make sure sites using our Deltanji source code management tool are aware of, is that the procedure can result in class dictionaries of remote databases being upgraded to a dictionary version that the instance hosting the databases cannot handle. Our Deltanji documentation now includes this paragraph in the section about InterSystems platform upgrades: Before upgrading an InterSystems IRIS, Caché or Ensemble instance we strongly recommend that you first disable all ECP connections the instance makes to other instances. Leave these connections disabled until after you have completed the upgrade, including execution of any post-upgrade steps recommended by InterSystems such as the recompilation of code in all namespaces. These precautions should prevent the upgrading instance from inadvertently upgrading class dictionary entries and routines on remote instances which may still be running an earlier InterSystems platform version.
go to post John Murray · Oct 4, 2022 And for extra convenience, follow the steps given in the Extension's README to enable the use of proposed APIs (view them here, or on the Details tab of the extension's page in VS Code). Then you can use the VS Code quickpick that Ctrl+p or Cmd+p opens (NB unshifted 'p'), type `String` and you should be able to open it directly.
go to post John Murray · Oct 4, 2022 Here's what I recommend (assumes you are using Server Manager extension as well; can be done without it but you'll have to edit JSON in a file): In Server Manager's tree, expand the namespaces of your server. Clock the "eye" icon on the %SYS row. This will add another root folder to your VS Code workspace. The folder uses the `isfs-readonly` scheme to access the namespace directly. In VS Code's Explorer (not ObjectScript Explorer), expand that folder and drill down to find the class you want. Assuming you want to use this multi-root workspace again, use "Save Workspace As..." from the File menu. If you don't, you'll be prompted when you exit VS Code and given a choice of saving or discarding.
go to post John Murray · Oct 4, 2022 Good video. One tip I have is that at 4:18 it advises using a command to add second and subsequent folders to a multi-root workspace. Instead I recommend clicking on the InterSystems Tools icon in the Activity Bar, then using the Servers tree (contributed by the Server Manager extension) to find your server and namespace, then clicking the pencil button (Edit Code in Namespace). This adds an isfs entry to your workspace. The eye button alongside it will add an isfs-readonly entry instead. Indeed you can do the whole of the workspace creation from that tree. With nothing open in VS Code (no folder, no workspace) click all the pencils or eyes you want. To name and save your workspace use "Save Workspace As..." from the File menu. If you haven't done that by the time you close the VS Code window you will be prompted to save or discard the as-yet-untitled workspace. So if you just wanted to browse a server speculatively you can use an untitled workspace and discard it when you exit.
