Both.

$SELECT(
%source.userActionfourteen=1:"User action fourteen",
%source.userActionthirteen=1:"User action thirteen",
%source.userActiontwelve=1:"User action twelve", 
%source.userActioneleven=1:"User action eleven", 
%source.userActionten=1:"User action ten", 
%source.userActionnine=1:"User action nine", 
%source.userActioneigth=1:"User action eigth", 
%source.userActionseven=1:"User action seven", 
%source.userActionsix=1:"User action six", 
%source.userActionfive=1:"User action five", 
%source.userActionfour=1:"User action four", 
%source.userActionthree=1:"User action three",
%source.userActiontwo=1:"User action two",
%source.userActionone=1:"User action one", 1:"Other")

I agree.

$CASE(1,
%source.userActionone:"User action one", 
%source.userActiontwo:"User action two",
%source.userActionthree:"User action three",
%source.userActionfour:"User action four", 
%source.userActionfive:"User action five", 
%source.userActionsix:"User action six", 
%source.userActionseven:"User action seven", 
%source.userActioneigth:"User action eigth", 
%source.userActionnine:"User action nine", 
%source.userActionten:"User action ten", 
%source.userActioneleven:"User action eleven", 
%source.userActiontwelve:"User action twelve", 
%source.userActionthirteen:"User action thirteen",
%source.userActionfourteen:"User action fourteen", :"Other")

But the result will still be only one value, even if all %source.userActionXXX=1.

What result should $select return if the conditions %source.userActionone=1 AND %source.userActiontwo=1 are true ?

Strange. I just checked on Caché Studio 2014.1.5 and Caché 2014.1.5 (logged in under superuser) - output

CSTUDIO.EXE

Unfortunately, version 2024.1 does not support like_regex

s json=[
{"s":"iPhone1"},
{"s":"iPhone2"},
{"s":"IPHONE3"},
{"s":"IPHONE4"},
{"s":"Phone5"}
]

d ##class(%ASQ.SetUtils).pp(json.apply("$[*]?(@.s like_regex '\p{LL}\w+')"))

[
{
"s": "iPhone1"
},
{
"s": "iPhone2"
}
]

I found something: Using a SQL/JSON Path Language Expression

Check the result outputs of the following code from Studio and from Terminal:

w $zu(67,13,$j)

Credentials are not requested, as most likely your existing session has not expired yet. By default, the timeout is 1 hour (see the "WebTerminal.Engine:WSKEYEXPIRES" class parameter).

I would venture to assume that this difference is due to the overhead of calling the class method. In other words:

• ##class(%DynamicArray).%New() -> ..%OnNew() -> $ZU()
• [] -> $ZU()

You have two mistakes.

• Instead

  for {i=1:1:%count set x=

  should be

  for i=1:1:%count {set x=

• Macros ≠ Function

A working example:

  #define MyLoop(%count,%result) set ref="",%result="" for i=1:1:%count set ref=$order(^%SYS("JOURNAL",ref),-1),%result=%result_$listbuild(ref)

  $$$MyLoop(5,x)
  write $listtostring(x)

Example of @Robert Cemper compiles without errors for me (even on Caché 2018.xxx):

Class dc.a [ Abstract ]
{

ClassMethod Test()
{
  #define MyLoop(%count) set x="" for i=1:1:%count set x=$order(^%SYS("JOURNAL",x),-1) write x,! 
  $$$MyLoop(5)
}

}

Show your code with the for loop that doesn't work.

If the array is multidimensional, then you can't do without loops (the code is without error handling):

  #define ArrayToStr(%arr,%str) set ref=$name(%arr),%str="s " for  {set ref=$query(@ref,1,val) quit:ref=""  set %str=%str_$$FormatName^%qcr(ref,1)"="##class(%Utility).FormatString(val)_","} set $extract(%str,*)=""
  #define StrToArray(%str) xecute %str

Usage:

  set a(0)=7
  set a(1,"color")="green"
  set a(1,"color","green")=""
  set a("color",$listbuild($double(3)))=$listbuild("red","blue")

  $$$ArrayToStr(a,str)
  zwrite str
  kill a
  $$$StrToArray(str)
  zwrite a

I would like to have *inc file entry to convert an array into a string and string into an array.

  #define Array1ToJSONString(%arr,%json)##continue
  s ##unique(new)=##class(%ZEN.proxyObject).%New()##continue
  d ##unique(old).%CopyFromArray(.%arr),##continue
    ##class(%ZEN.Auxiliary.altJSONProvider).%WriteJSONStreamFromObject(.%json,##unique(old))##continue
  s %json=%json.Read(3641144)
  
  #define JSONStringToArray1(%json,%arr)##continue
  d ##class(%ZEN.Auxiliary.altJSONProvider).%ConvertJSONToObject(%json,,.##unique(new)),##continue
    ##unique(old).%CopyToArray(.%arr)

Usage:

  set a("color")=$listbuild("red","blue")
  set a("price")="expensive"
  set a("size")=$listbuild("large","small")
    
  $$$Array1ToJSONString(a,jsonStr)
  zwrite jsonStr
  $$$JSONStringToArray1(jsonStr,b)
  zwrite b

Class dc.a Extends %Persistent [ SqlTableName = observation_lab ]
{

Index iCode On code;

Index iCodeText On codetext;

Property code As %String(MAXLEN = 2000);

Property codetext As %String(MAXLEN = 2000) [ SqlFieldName = code_1_text ];

/// d ##class(dc.a).Test()
ClassMethod Test(N = {5e6})
{
  s t=$zh
  d DISABLE^%NOJRN
  k ^dc.aD,^dc.aI
  f i=1:1:N s c=i-1#1000+1,^dc.aD(i)=$lb("",c,"code_1_text_"_c)
  s ^dc.aD=N
  d ENABLE^%NOJRN
  w "(time) insert = ",$zh-t,!
  
  s t=$zh
  d ..%BuildIndices(,,,$$$NO)
  w "(time) %BuildIndices = ",$zh-t,!
  
  s t=$zh
  d $system.SQL.TuneTable("dc.observation_lab",,1,,,,,,,"100%")
  ;&sql(TUNE TABLE dc.observation_lab %SAMPLE_PERCENT '100%')
  w "(time) tune table = ",$zh-t,!
}

}

The following query does not use iCode/iCodeText indexes (2025.2.CE):

select code_1_text, count(code_1_text)
  from dc.observation_lab
  group by code_1_text
  order by 2 desc

PS: if possible, I would try to convert the text into a number in some way and index this number already, perhaps even with the bitmap type.

I think this should be addressed to the WRC rather than the Ideas Portal. Also, @Robert Cemper has already registered WRC #1002589 and @Evgeny Shvarov most likely has too.

I completely agree with you.👍

I hope someone from InterSystems will pay attention to your post.

PS: and in addition, it would also be nice to solve the issue with %FromOref(): either the code or the documentation needs to be fixed. On version 2025.2.CE it still doesn't work.

Here explained to us that this is not a bug, but a feature: <PROTECT> *Function not allowed in IRIS Native python

Starting from 2024.1 IRIS Native disallows routine invocations. Please use class methods instead.

For reference, these changes can be identified as DP-422635 and DP-424156.