It the issue of this question/post the "?wsdl" not working or that the SOAP pass-through does not work?

To get "?wsdl" to work you need an HTTP pass-through, technically it's not a SOAP call.
In fact the "?wsdl" parameter is interpreted by IRIS and you get the "wsdl" returned by EnsLib.SOAP.GenericService. 

I created the production and tested the call to the SOAP service (I'm using 2024.1 but I don't thin is relevant) and it works.
I'm using SOAP UI to call the service through the IRIS production and I get the correct result.

Apart from the "?wsdl" call, have you tried calling the actual SOAP service?

For simple cases I found that often using a HTTP pass-through instead of SOAP pass-through makes thing easier.

%ResultSet in deprecated, use %SQL.Statement instead.
Never concatenate parameters to query text, use placeholders ("?").

Set sql = "SELECT COUNT(*) FROM "_tableName_" WHERE "_fieldName_">=? AND "_fieldName_"<=?"
Set resultset = ##class(%SQL.Statement).%ExecDirect(,sql,fromDate,currentDate)
Do tResult.%Display()

I came across this old question and I was (almost) shocked by the answers because we are considering using System Default Settings for a project and one of the settings value we need to customize per system is Pool Size!

Fortunately things have changed since this was posted an now Pool Size can be defined/configured in System Default Settings and this is also documented:

Settings That Can Act As System Overrides

I'm not sure when this has changed,I believe this has been implemented in 2024.1, the version I tested and it works.

The behavior of this default setting a a little different then others (cannot be modified/overridden from within the production settings) but, IMHO, that's fine or even better!

I'm writing this to warn anyone using a recent product version looking/reading this question that now, from 2024.1 Pool Size can indeed be configured in System Default Settings.

Hi @Aya Heshmat , please consider adding the host Pool Size in the Production Configuration page as it once was.

For details on this topic see my post/discussion:

Display Pool Size in Production Configuration page

and related Idea:

Add pool size in production configuration page

For us is REALLY important, at the moment (where we can) we have hacked/changed the Prod. Config. Portal page, in the future with the new modernized page this change may be difficult to implement/hack.

It's difficult to tell if the bad value is in the passed parameter or in the returned value.

Just as curiosity, what's the value of pRequest.Warehouse and what's the datatype of Warehouse column in the prod.stocks table?

I doubt it can be done with a generic process for any VDOC type.

For HL7 to get Virtual Property Path using names ("symbolic ones") you must know and use the "DocType" (that is the schema category and message structure) of the message.

In HL7, for a given HL7 message, it's not clear to me what you need/want as output, you want to visit all nodes/fields....defined? All possible nodes/fields defined in the schema structure? All nodes/fields that contains values?

If you need all possible nodes/fields for a given DocType, then you can get them from the Schema Definition.

For training and certification you get a corresponding Credly badge that you can add/share in your Developer Community profile or your Linkedin and other social accounts.

When you take an InterSystems training course you get attendance badge, for example:

Building and Managing HL7 Integrations Training

Certification is separate from training, when you pass a certification exam (performed by a third party entity) you get the corresponding certification Credly badge, for example:

InterSystems HL7® Interface Specialist

If the SetValueAt() method is not working I guess it's also returning an error, my suggestion is to check the returned error, so:

Set sc=tOBXSegment.SetValueAt(tOBXText, 5)
Do $system.OBJ.DisplayError(sc)

I wish I could see the code in $$macroERROR^%occMsgXML() (used by $$$ERROR() macro and other) to store the stack in a Status.

Hi Scott,

I don't consider 255 as larger than the typical string length and I'm surprised of your issue and I don't fully understand your code, probably because it's not complete (set tSC = rs.Insert(pInput) make no sense to me).

Anyway, my suggestion is to find some more info that may give you some hint.

For example I'd add the following lines in your OnProcessInput() method:

Set colId=pInput.GetColumnID("ExternalName")
$$$LOGINFO("ColumnType is "_pInput.GetColumnType(colId))
$$$LOGINFO("ColumnSQLType is "_pInput.GetColumnSQLType(colId))
$$$LOGINFO("ColumnSize is "_pInput.GetColumnSize(colId))

Please test this using a query that extract a few records to avoid flooding your event log.

I'm curious to see what you get.

Can you please provide some more details on "columns that are larger than the typical string length"?

How long (max) can be?
What's the data type for these columns in the external database?
What database are you connecting to? Using ODBC or JDBC?

Can you please define "Unique/distinct message counts"?

Hi @Muhammad Waseem , nice and useful article.

Please note that for embedded SQL, since some version 2020.1, when the Universal Query Cache was introduced, it's no longer true that "SQL statements are pre-compiled into the program during development", please check relevant documentation.
 

You can find more details and a discussion of this topic, including comments from @Dan Pasco, the initial dynamic SQL developer, in the post A look at Dynamic SQL and Embedded SQL