there is of course %LIbrary.ArrayOf.*

for example

https://docs.intersystems.com/iris20241/csp/documatic/%25CSP.Documatic.c...

unlike %Library.List* of which allows for an item to exist more than once in the set/collection

The linkage definition is stored in a class which can be found here

you could use System Explorer->Classes to export the class as a file and then use System Explorer->Classes to Import the class.

Depending on your implementation you can 

• If using %SQL.Statement set %SelectMode accordingly
• if using the old %Library.ResultSet, set RuntimeMode accordingly

in your method code.

Using  [ Language = python ] in a classmethod and then leveraging pymongo could be one way to do this

If you click on the bottom line of VS Code where your connection is defined it will display a dialog on the top of the screen showing the Server Actions including the SOAP Wizard 

Try this but I might be incorrect.  It looks like you have a custom component which you have highlighted.  When you compile the component class it produces a .js file in InstallDirectory\CSP\broker.  Look there to see if the file is there.  If not consider recompiling your component class and ensure that the .js class exists.

I've used ChatGPT for some IRIS related things.. Sometimes it's been useful and some times its simply made up stuff, it made up the names of classes in IRIS that have never existed and do not exist in the most recent version.  Other times it's provided me some information that wasnt boiler plate to copy and paste but led me down a path that allowed me to find the solution.

There is in fact a global on the Registry that has a record of the Patient data each time it is changed, the global is ^HS.Registry.Patient.OldHistory

following https://docs.intersystems.com/iris20233/csp/docbook/Doc.View.cls?KEY=RSQ...

An existing row is one in which the value being inserted already exists in a column that contains a unique constraint. For more details, see Uniqueness Checks.

the way to understand this is to determine what resource is required to access the database associated with /database/db4/syb/.  You can find this out by going to System Administration->Configuration->System Configuration->Local Databases and view the table that is associated with /database/db4/syb/.  You should see something like

find your and find the Resource then add the Resource to the Role you are connecting with.  While adding %All as a role will prevent the error it will also grant a whole lot more permissions than just the <protect> error.  

I commonly will use COALESCE in my SQL statements when I want to define an default value, as an example I would do

SELECT COALESCE(Amount,0.00)

If you are describing your globals in a class and they do not use default storage, but rather SQL Storage(%Storage.SQL) you can define your storage to include extended references.  This is a technique that I have used in the past.  How you loop thru the extended references is up to you.  In my case we took advantage of the ability to SetServerInitCode which is called once when the connection is made to the server, there is an equivalent capability in DeepSee/Analytics.  In our ServerInitCode we populated an array of the different extended references we needed to access and our storage map firstly looped thru this structure and then the actual global.

you could construct this with usage of <hgroup> and <vgroup> if you had a fixed number of rows.  

If you had a variable number of rows you could use a tablePane where the resultset object returns the rows with the first column being the label and the second column being the cost value for items.

Users are added via HSPI Management->Settings -> System Mode->Configuration->Assignment Username  https://docs.intersystems.com/hs20222/csp/docbook/DocBook.UI.Page.cls?KE...

this data is found in Ens_Config.Item

The class query EnumerateCategories in Ens.Config.Production should provide what you are looking for.

If those fields are not used in the ReportDisplay, ie the HTML or PDF output, you could consider removing them from the ReportDefinition.  If on the other hand, you do need these fields then leave them in.  However, something else seems to be going on.  I commonly have this style of ReportDefinition

The usage of <macrodef > just allows me to have a single set of code that injects the same attributes into the <Master> node.

When running the report in XML mode it produces

<Master runDt="10/13/2022" footerDate="October 13, 2022" runTm="08:47AM" runBy="_SYSTEM" Draft="" ISCPrime="0" Instance="HEALTHSHARE" Namespace="HSEDGE1" Server="LAPTOP-ET8APOSR" InternalURLLinkPrefix="http://localhost:52773" CustomerName="Ready Computing, Inc" CoverPageDate="October 13, 2022" CustomerLink="" PageNumbering="1" SystemMode="" FilterSpecDisplay="" ReportName="Ensemble Message Management" HeaderLine2="" Top="9999999999999" ReportClass="RC.Ens.Report.MessageManagement" ZVERSION="IRIS for Windows (x86-64) 2021.1.2 (Build 336_0_21564U) Tue Apr 12 2022 12:13:45 EDT" ReportTitle="">

I don't think attributes found in the root node, in my case Master, are emitted to the Excel file.

If I run the report in MODE=XLSX mode it produces.. note it does not show the attributes 

so this is answering your question regarding your attributes at the top level.  Your question regarding the elements at the ProssData node is something different.  In my example, if I change 

to 

and then run the report in XLSX mode the attributes Namespace and TaskId do not appear in the Excel file.  However, I would have to change the ReportDisplay so that I now reference

@Namespace and @TaskId

if I want the PDF and HTML output to work properly.

when looking at the code in  %ZEN.Component.toolbar it looks like the class is hard coded and can't be changed.. but I could be incorrect.  Using a modern UI framework like Angular or so many others would allow you greater control.

ZEN reports provide a number of methods to generate reports including GenerateReportToFile.  This method allows you to specify the outputfile and mode.

Can you elaborate on what you mean by "hide" any component under ReportDefinition.  The ReportDefinition is where you define the XML document that will be created that is later used by ReportDisplay to output the data for a PDF report, Excel utilizes the ReportDefinition.   Just because you have an entity(element/attribute/group) in a ReportDefinition doesn't mean it will be utilized in the ReportDisplay.

You can look at the contents of zenutils.js to see the actual details of the zen(id) function.