I submitted OEx updates to the details of both my entries earlier today, merely adding an online demo link for each. Both updates are still showing as awaiting approval. Please add that bonus to DX Jetpack for VS Code and IPM in VS Code.
Here's a technique I previously wrote up, maybe useful until IPM supports this scenario itself.
https://community.intersystems.com/post/can-zpm-ipm-package-be-required…
No, nothing else new in it. Were you able to connect but not work? Or wasn't it possible to connect? If the latter, perhaps the server had run out of licenses.
@Vadim Aniskin thanks.
I just posted a first video at https://www.youtube.com/watch?v=w4w1oSRqoak
A new version of the ObjectScript was published on Marketplace yesterday to fix this issue.
"isfs" stands for InterSystems File System. It is an implementation of VS Code's FileSystemProvider API which enables extensions to provide virtual filesystems.
More information near the end of the page at https://code.visualstudio.com/api/extension-guides/virtual-documents
I suggest you ask the Cody extension authors whether they support FileSystemProvider-sourced documents.
The clone url above seems to be for a different repo.
Anyone suffering from this and who hasn't downgraded to VS Code 1.92.2, or who has but is willing to upgrade to 1.93 again, please see https://github.com/intersystems-community/vscode-objectscript/issues/14…
Unless we get adverse reports about that beta VSIX we plan to publish a non-beta build of it on Marketplace early next week.
A couple of days ago I entered a new version of DX Jetpack for VS Code which adds three completely new extensions.
Currently the workaround is to downgrade your VS Code to 1.92.2. More info here:
https://code.visualstudio.com/docs/supporting/faq#_how-do-i-opt-out-of-…
Please follow this issue:
https://github.com/intersystems-community/vscode-objectscript/issues/14…
There is an open GitHub issue requesting this, so probably not yet available.
https://github.com/intersystems-community/openexchange/issues/123
Maybe similar to https://community.intersystems.com/post/my-intersystems-learning-lab-do…
Is your learning lab instance reachable through IRIS Portal?
If you open the browser's DevTools (usually achieved by pressing F12) does that reveal any errors when you try accessing the page?
Well done all. I wonder if we'll see improved versions of any of these apps in the 2024 Grand Prix (assuming there's going to be one this year).
Not with Studio, but if you use VS Code, enable proposed APIs, and create a multi-root workspace with one folder for each namespace then I think you can search across them all.
I expect the IRIS Portal URLs for these two instances look like this:
In that case, use the bold section as the "pathPrefix" property within the "webServer" object in the server's entry in the "intersystems.servers" settings object.
When setting up a connection definition step-by-step this part is referred to as Path prefix of instance.
See https://docs.intersystems.com/components/csp/docbook/DocBook.UI.Page.cl…
Windows users who need to use IPM/ZPM to install packages that pull in Python packages may want to hold back from adoption of 2024.2 until https://github.com/intersystems/ipm/issues/540 gets closed and an updated IPM ships.
On this screen of yours:
.png)
does "Open" succeed?
If not, get back to that screen and try "New", then create a new production in a new package, e.g. Robert.PlayProduction
Can you use the configuration page on that?
When you get this prompt:
Global ^
Please type exactly this:
EnsPortal.Settings(,"LastProduction")
Then press Enter.
When you access the IRIS Portal of your local instance from a web browser, what is the browser URL?
You seem to have omitted the crucial caret symbol required between the HELP and the %G
This is caused by how version 2.12.0 and above of the ObjectScript extension depends on the Server Manager extension, which hasn't yet been made compatible with VS Code in the browser.
I have created https://github.com/intersystems-community/intersystems-servermanager/is…
Workaround is to use the gearwheel on the extension's detail page, then choose to install the latest pre-2.12 version.
I also spotted an apparent typo in line 660 in the second screenshot. See if you can too.
@Ben Spead sometime we'd love to show your Internal Apps team the kind of codebase insights Yuzinji can provide. Please DM me if you are interested.
Maybe the page is trying to display details of a previously-opened prodclass that is giving it a problem.
I suggest you use the %G utility in an IRIS Terminal in your namespace (INTERFACES?) to see what this lists:
INTERFACES>d ^%G
Device:
Right margin: 80 =>
Screen size for paging (0=nopaging)? 24 =>
For help on global specifications DO HELP^%G
Global ^EnsPortal.Settings(,"LastProduction")
^EnsPortal.Settings("XXX","LastProduction")="Foo.Bar"
Global ^Other answers here cover exporting the application definition.
To transfer the application files it may be simplest to copy the files from the host OS path that the application definition points to.
Another option is to create a Studio project, add the webapp to the project, then export the project.
But your earlier screenshots show you trying to create entities in the INFORMATION.SCHEMA package and in the %Api package. These are always mapped to the IRISLIB database (see the error dialogs), which is always readonly.
You should enter a non-percent package name of your own (e.g. Robert).
When you created your Production, what package did you put it in?
@Timothy Leavitt here's the report showing which IRIS 2024.1 deprecated classes your Test Coverage Tool 3.1.0 package uses.
.png)