What platform (Operating System) are you using for IRIS?

I think NTLM authentication is not available in IRIS for Linux.

According to the documentation, it's not possible exporting an object.

Edit: however, as pointed out by @Herman Slagman in the next post, it's indeed possible, I'm going to provide feedback to documentation team.

You can manually create the XML document using %XML.Writer, like:

	set writer=##class(%XML.Writer).%New()
	set writer.Indent=1
	set writer.NoXMLDeclaration=1
	set status=writer.OutputToDevice()
	set status=writer.StartDocument()
	set status=writer.RootElement("XMLTest")
	set status=writer.Element("Id")	
	set status=writer.WriteAttribute("Attribute","D1949EE1-7D03-4666-9548-D1A949E10327")
	set status=writer.EndElement()
	set status=writer.EndRootElement()
	set status=writer.EndDocument()

The output of the above code is:

<XMLTest>
  <Id Attribute="D1949EE1-7D03-4666-9548-D1A949E10327"/>
</XMLTest>

Having said that, what's your issue with the closing tag? Semantically there is no difference, any system should be able to handle both cases (with or without closing tag).

My guess is that your %var local variable array is in conflict with the code executed by the embedded sql.

As you may know % local variables have global scope, therefore should be used with caution, particularly when calling "other code", like embedded sql in your case.

If a global scope % variable is needed, is advisable to follow the documentation on Local Variable Naming Convention:

Variable names starting with the % character are known as “percent variables” and have different scoping rules. In your code, for a local percent variable, start the name with %Z or %z; other names are reserved for system use.

I suggest to change your variable to %zvar or similar, if you do not need global scoping, remove the leading %.

Ciao Pietro,

difficult to tell without looking at the code.

Looking at the response my guess (bet?😉) is that your code  has some error processing and if "somewhere" an error status is returned, then the error processing is triggered and is returning the response you see, including headers etc.

In the documentation site (every page?) there is a "Feedback" blue button on the right of the page, click on it...

What's the status returned by the Send() method of %Net.SMTP class?
I believe it should contain some info.

Another option in one line:

do ##class(%SYS.Namespace).ListFunc().%Display()

What operating system? What InterSystem product? What Version?

Your Business Operation (is supposed to) use the EnsLib.EMail.OutboundAdapter, but the in the code you use the %Net.SMTP class directly, ignoring the adapter.

In the Interoperability portal your implementation  provide the email adapter configuration (server, certificate, credentials etc. etc.) that in fact are then ignored in the code. This makes it very confusing for anyone using the portal, now...and in the future!

So the first question is, do you want to use the EnsLib.EMail.OutboundAdapter or not?

If you want to use the adapter, if you have not already done it, I suggest to start with the documentation:

Using the Email Outbound Adapter and Settings for the Email Outbound Adapter

If you don't what to use the EnsLib.EMail.OutboundAdapter, then remove the reference from your code.

Using %Net.SMTP class directly (right?), you said that "...I get the error that the property UseSTARTTLS is not available." and this is very strange, can you confirm you are using IRIS version 2021.1?
Is your code the same as in your first post or has changed? If changed, can you post the modified code that fail?

Last but not least, are you sure your outlook.com account allow user/password authentication? Or you must use OAuth2 authentication??

From Stream Compression documentation:

.....new stream data is automatically compressed, except for the following cases, where the data is not suitable for compression:

• The stream can be stored in a single chunk less than 1024 characters long.
• The stream is already compressed, that is, the first chunk of data matches a typical compressed file format, such as JPEG, MP3, or ZIP.
• The first 4KB of the stream cannot be compressed by at least 20 percent.

I guess your test runs into these cases.

To call a class method the syntax is:

##class(ClassName).MethodName(params)

Use XML format and you get 6x faster load than using UDL.

My guess the difference is due to the parsing needed by UDL import.

My estimate in your case you can get as low as 42 seconds, I'm curious to see the actual numbers.