Try enabling the service %CallIn:
To prevent IRIS_ACCESSDENIED errors while running Embedded Python, enable %Service_Callin. In the Management Portal, go to System Administration > Security > Services, select %Service_CallIn, and check the Service Enabled box.

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls...

Hi!

I can't see the benefits of calling a SP (!!!) instead of "normal" cache code:

Set file = ##class(%File).%New("c:\temp\test.csv")
Set sc = file.Open("R")
While 'file.AtEnd {
       Set line=file.ReadLine()
}

Hi Alexander,

before running the second command, and in order to get the right numbers, shouldn't you clear the buffers so system takes it again from the disk?

d ClearBuffers^|"%SYS"|GLOBUFF()

I'd be interested in that too. There must be an utility that simply emulates what the patient viewer is doing, so calling it using the MPIID should give back all the information from a patient, including demographics and encounters data.

I simply can't find it, but I'm pretty sure it's there. Anyone knows?

I use this on Windows to automatically restart any instance. Probably simply changing "\" by "/" will do the trick, and change stopstart for stop:

//restart instance
d ##class(Ens.Director).StopProduction(1,1)
set cmd=$P($ZU(12),"\",1,$L($ZU(12),"\")-2)_"\bin\iris stopstart "_$P($ZU(86),"*",2)
d $zf(-2,cmd)

Hello,

I know it's quite old and maybe it's solved, but I had a similar issue with the message ERROR #815: User not authorized for service %Service_WebGateway

In my case, the problem was in the resources setup (/csp/sys/sec/%25CSP.UI.Portal.Resources.zen). By giving public permission to the gateway , the system started to work:

Hope this helps!

Just for fun, or to see if AI matches the experts, I've asked the question to Mixtral. This is what it is explaining:

Yes, I can certainly explain the difference between %ResultSet.SQL and %SQL.Statement in Intersystems Cache ObjectScript.

%ResultSet.SQL is a class that provides a result set interface for executing SQL queries. It allows you to iterate over the rows returned by a SQL query and access the columns as properties of each row. Here's an example of how to use %ResultSet.SQL:

SET rs = ##class(%ResultSet.SQL).%Open("SELECT * FROM mytable")
DO WHILE (rs.%Next()) {
    SET column1 = rs.column1
    SET column2 = rs.column2
    // Do something with the columns
}
rs.%Close()

On the other hand, %SQL.Statement is a class that provides a statement interface for executing SQL queries. It allows you to prepare a SQL statement and then execute it multiple times with different parameter values. Here's an example of how to use %SQL.Statement:

SET stmt = ##class(%SQL.Statement).%New()
DO stmt.%Prepare("SELECT * FROM mytable WHERE column1 = :val1 AND column2 = :val2")
DO stmt.%Execute(val1, val2)
DO WHILE (stmt.%Fetch()) {
    SET column1 = stmt.column1
    SET column2 = stmt.column2
    // Do something with the columns
}
stmt.%Close()

In summary, the main difference between %ResultSet.SQL and %SQL.Statement is that %ResultSet.SQL is used for iterating over the rows returned by a SQL query, while %SQL.Statement is used for preparing and executing a SQL statement multiple times with different parameter values.

This is great Kurro!

But this is the kind of things I would definetely take advantage of embeded python to speed up the development. To send a message using python, few lines of code are needed:

import pymsteams
myTeamsMessage = pymsteams.connectorcard(url) # Initialize the connector card with webhook URL
myTeamsMessage.text("This message will end up in team") # Message content
myTeamsMessage.send()   # Send the message