go to post John Murray · Jan 23, 2023 Still no ARM64 version of the Community Edition of this build? (Asking for a friend; my employer hasn't bought me an M1 / M2 machine yet )
go to post John Murray · Jan 23, 2023 One of my colleagues just tried using the registration link but got this response from the Global Masters page it leads to:
go to post John Murray · Jan 16, 2023 You could use the technique I described in https://community.intersystems.com/post/class-projections-and-projection...
go to post John Murray · Jan 13, 2023 For VS Code's native Search facility to search the server-side code your ISFS workspace gives you access to you must follow the instructions in the "Enable Proposed APIs" section of the extension's README (which is also available here). One of the steps will have to be repeated each time your InterSystems ObjectScript extension gets upgraded from MarketPlace with a new version.
go to post John Murray · Jan 12, 2023 my guess that if we specify port 57772 as the default port in the web server which I'm assuming that would be Apache , we don't have to specify the port in our url No, if the web server (Apache or any other server) is listening on any port other than 80 (for http protocol) or 443 (for https protocol) your URL needs to tell the client app (e.g. your web browser) to connect to a port that is not the standard one for the specified protocol.
go to post John Murray · Jan 12, 2023 Image (here and on Global Masters) incorrectly shows the time as 4:00 pm CET.
go to post John Murray · Jan 11, 2023 Also, server-side editing mode can deal with CSPs. See https://intersystems-community.github.io/vscode-objectscript/serverside/..., or if you use Server Manager's "pencil" button alongside a namespace in order to create your isfs workspace, hold the Alt key down when clicking it and you'll get a workspace folder which shows you the CSP app files.
go to post John Murray · Jan 11, 2023 Mark, if you are using the server-side editing paradigm, which matches what you're used to with Studio, make sure you follow the instructions in the "Enable Proposed APIs" section of the extension's README (also available here). Until you have done this the Ctrl/Cmd+P technique mentioned by Dmitry won't find anything when you are working server-side.
go to post John Murray · Jan 10, 2023 Yesterday I noticed 2022.3.0.584.0 on Developer Download and today build 589 appeared there and also on containers.intersystems.com Is this Preview #5?
go to post John Murray · Jan 6, 2023 Does WinSQL use ODBC? If so, does the ODBC driver need to be upgraded?
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.
