Thanks for the reply.

We have a custom function that was developed for a different purpose but will do what I need for the current use case. It will be a more succinct solution than using a foreach action.

I'm trying to do something similar, but the condition is checking the number of OBX segments in messages that can contain multiple ORC groups. The condition pasted below does not work. It also does not work if I replace the curly braces with parentheses. The only way it works is if both a PIDgrpgrp index is included and an ORCgrp index is included, and only if the outer punctuation characters are curly braces, not parentheses. We're on HealthShare version 2023.1.3.

We sometimes export classes from one environment and import them to another. I don't see .cls as a supported file type for those activities.

I feel that I have not explained clearly enough the Studio features that we use. We often export classes to XML files. Similarly, we import XML files, compiling them as classes during import. I didn't mean to imply that this was done simply to transfer classes to other namespaces or servers. Rather, it's a way to archive classes as XML files. (We don't use a source control system.)

We use the Find in Files utility to determine the classes and other files in which a given string exists.

I mentioned the Namespace variation of the Studio Workspace pane because that is the arrangement of files (classes, lookup tables, message schemas, etc.) that we most often use.

I've never used VS Code, and I don't know anything about it. I am wondering whether there are equivalents for a couple things we often do in InterSystems Studio:

• Export (to XML) and import classes.
• Find in Files.

Also, is there an equivalent to the Namespace Workspace that is available in Studio? That's the arrangement we use the most.