WARNING: Bug in IRIS Native API

I while back InterSystems added some new resources to add more security for Native API
You may need to add them

1 0

quite an interesting hidden feature.

Though testing with _SYSTEM/SYS and %All, this had no visible impact
It is exactly 1 method that breaks in all 4 Nativ packages
And with %All the rest is available anyhow and working fine.

BUT eventually %All is not All enough

1 0

Vitaliy Serdtsev · 10 hr ago

Here explained to us that this is not a bug, but a feature: <PROTECT> *Function not allowed in IRIS Native python

Starting from 2024.1 IRIS Native disallows routine invocations. Please use class methods instead.

For reference, these changes can be identified as DP-422635 and DP-424156.

PS: and yes, additional roles and resources like %Native_*/%All etc. no eliminate the <PROTECT> error. Checked on version 2025.2.CE

2 0

Robert Cemper · 9 hr ago

Thank you for the explanation. @Vitaliy Serdtsev 🙂👍
This matches my investigations

0 0

Robert Cemper · 9 hr ago

It might be great to remove the related refences also
from official documentation
Py
https://docs.intersystems.com/components/csp/docbook/Python-Native/v1.0.0/irisnative.iris.html#irisnative.iris.function

Nodes.js
https://docs.intersystems.com/components/csp/docbook/NodeJS-Native/v2019.2/external-_intersystems-iris-native_.Iris.html

Java
https://docs.intersystems.com/iris20201/csp/docbook/DocBook.UI.Page.cls?KEY=BJAVNAT_call#BJAVNAT_call_function

.NET
https://docs.intersystems.com/iris20201/csp/docbook/DocBook.UI.Page.cls?KEY=BNETNAT_call#BNETNAT_call_function

Also Class reference for 2025.1
https://docs.intersystems.com/iris20251/csp/documatic/%25CSP.Documatic.cls?LIBRARY=%25SYS&CLASSNAME=%25Net.DB.Iris#Function

like this:
Calls a function (label^routine), passing zero or more arguments and returning the function's return value. Trailing arguments may be omitted, causing default values to be used for those arguments.

This method throws an exception when an error condition is encountered.

routineName	input	The name of the routine that implements the function to be called.
functionName	input	The name of the function to be invoked.
args	input...	The arguments to be passed to the method.
	return	The value returned by the `functionName` function.

Such a misleading documentation roughly 1.5 years behind reality is not so impressive
It took days to find this out. 😖

0 0

Vitaliy Serdtsev · 9 hr ago

I completely agree with you.👍

I hope someone from InterSystems will pay attention to your post.

PS: and in addition, it would also be nice to solve the issue with %FromOref(): either the code or the documentation needs to be fixed. On version 2025.2.CE it still doesn't work.

1 0

Irène Mykhailova · 7 hr ago

Hi @Vitaliy Serdtsev, could you please add this issue as an idea to the Ideas Portal?

0 0

Vitaliy Serdtsev · 7 hr ago

I think this should be addressed to the WRC rather than the Ideas Portal.
Also, @Robert Cemper has already registered WRC #1002589 and @Evgeny Shvarov most likely has too.

2 0

Robert Cemper · 6 hr ago

Suggested Idea: Keep documentation in sync with reality .. ? 🤭

4 0

Nick Petrocelli · 3 hr ago

I would recommend reporting this on the docs feedback page: https://docs.intersystems.com/irislatest/csp/docbook/Doc.Feedback.cls

In my experience they are very responsive to this kind of feedback

1 0

Ben Spead · 2 hr ago

I completely agree! Doc offers a direct channel to them for feedback, and they are very responsive to that.

Every documentation page has a Feedback button on the right, which will capture the page from which the feedback originates, making it even faster for the Docs team to know where a tweak is needed:

0 0

Robert Cemper · 1 hr ago

AH, That was meant by feedback
Which is easy now, as it wasn't a bug but an explicit feature

0 0

Robert Cemper · 1 hr ago

The feedback button is not available for Python and for Node.js.
These were my 1st broken examples

0 0

Ben Spead · 5 min ago

got it - I reached out to the Docs team to better understand why the button isn't there

0 0