I wouldn't recommend using ZU commands as they are deprecated so they are not guaranteed to always work.

Errors returned can occasionally be COS error codes, or they might boil down to OS error codes. It depends on the function; I don't know if there's a universal method that differentiates. I think you need to look at what you're calling. Often the class reference gives details on what error codes to expect.

In your particular case, referring to the %Library.File.CopyFile class reference:

"This method returns true if it succeeds and false otherwise. Pass return by reference to obtain the low level return value in case of errors which is the negative value of the operating system return code."

My guess is this has something to do with your web application definitions in HealthShare, but I don't have any conclusive suggestions, so I'd second Pete's suggestion.

Hi Jeff,

You're including "index" in the string. You would need to concatenate it in for it to take its value, such as:
set addarray(1) = source.GetValueAt("PIDgrpgrp(1).ORCgrp(1).OBXgrp("_index_".OBX:ObservationValue(1)")

Hello Carl,

Take a look at the following docs regarding Ensemble management portal resources:

Controlling Access to Management Portal Functions

Hello Eriks,

Before any other investigation I would note that Caché 5.0.21 is an extremely old version and I am surprised it even works on Windows Server 2016 as that is far outside the range of supported platforms.

If you can reproduce the behavior on a modern version of Caché, or better yet IRIS, then there may be more to look into.

Hi Fernando,

Check out this other developer community article: How to Export and Import Ensemble Components and Productions

It includes a link to the documentation on deploying a production.

If you need to do this programmatically you'll want to review the Ens.Deployment.Utils class reference.

Hi Yone,

I just wanted to mention that zf(-1) is deprecated in modern versions in lieu of zf(-100).

Also, you might find the %Library.File methods/queries useful.

This other developer community post about purging backups contains some sample code for working with files, as well as a link to the relevant class reference:

https://community.intersystems.com/post/looking-good-routineclass-purging-cach%C3%A9-backups

Hi Tim,

Maybe you could try enabling tracing to get more information on what is happening.

Hello Stuart,

Your elseif appears to have a typo of obxIndex:

elseIF GetValueAt("OBX("_obxndex_"):3.1") = "SARD" {

Besides that, you can use * to count fields rather than loop through and manually count them.

Hope that helps.

Hi Scott,

Can you reproduce the compilation error not getting caught on save? When I try to save with a syntax error the rule set still saves, it does throw compilation errors however. Can you describe in more detail where the misplaced { was?

Re: your second question I'm not certain, but if the class failed to compile I'm not sure what kind of behavior we would expect from trying to use the rule set. Perhaps this is related to the particular state your environment was in.

Hello Yone,

While you can probably figure out a way to code this in a transform, I think it would me more straightforward and legible to write a custom utility function and put your looping logic there.

Ensemble Utility Functions