This is very confusing, I understand editing names for privacy reasons, but you are changing the actual format, not only names. I've never seen "##class(|"NS"|Path.To.Class)" in errors.

Can you reproduce the issue with a simple sample code using generic names? This way you can post your code so we can understand what's going on and how to fix/log the problem.

s %sc=##class(|"NS"|Path.To.Class).ClassMethod(..%p1,%p2)

Is this really contained in the error message? Is that your code?

To me |"NS"| and ..%p1 look strange.

Try with:

<Map Prefix="/v([0-9]{1,2})/news/([^/]*)"    Forward="API.Dispatch.news"/>

Try with:

<Map Prefix="/v([0-9]{1,2})/news/:id"    Forward="API.Dispatch.news"/>

Adding and Removing Settings 

😉

Stream compression is enabled by default since version 2021.2, see release notes:

Saving on Storage

Stream compression – is now on by default for all globals-based stream classes, with no application change required. Existing data remains readable and will be compressed upon the next write. Experiments with real-world data have indicated compression ratios ranging from 30% for short texts to 80% and more for XML and other document types.

It's the length (number of elements) on the (old format) list

Please check the relevant documentation:

Executing Stored Procedures

I've asked the DC AI chat bot and the answer is worth a look:

https://community.intersystems.com/ask-dc-ai?chat_id=1920

Note that using SQL Server ODBC you probably do not need to specify "IOType" in the param array.

If you still have problems, get back with a sample code of what you are doing.

Using the Wheel of Names, we've chosen one random lucky winner:

🏆 Random award goes to the idea Do not include table statistics when exporting Production for deployment by @Enrico Parisi 

🤣😂🤣😂

If you post an example of the code you are using maybe someone can help you understand the problem.

Never, ever, concatenate parameters to an SQL Query!

Fixed for you:

    Set sqlQuery = "SELECT * FROM %Dictionary.PropertyDefinition WHERE parent = ? ORDER BY SequenceNumber"
    Set resultSet = ##class(%SQL.Statement).%New()
    Set status = resultSet.%Prepare(sqlQuery)
    $$$ThrowOnError(status)
    Set tResult = resultSet.%Execute(className)
    
    While tResult.%Next() {
        Set Name = tResult.%Get("Name")
        ...
        }

Back to your initial question, what is your definition of "sorted by Storage"?

If you need the ($list) position of properties within the global, then your query does not answer your question.
I'm writing this in case other community members read this question/answer.

It takes a lot of imagination and fantasy to understand what you need without an example of (pipe delimited) input and (json) output.😉😊

Six 😟

Yes, pretty sure, that is what is taught in the ISC training courses and what the documentation says:

Description ($PROPERTY)
Property names are case-sensitive

Selecting Fields
Field names in a SELECT statement are not case-sensitive. SqlFieldName names and property names are case-sensitive.

Rules for Class Member Names
Note that the system preserves the case that you use when you define classes, and you must exactly match the case as given in the class definition. However, two class members cannot have names that differ only in case. For example, the identifiers id1 and ID1 are considered identical for purposes of (uniqueness.)

You probably have a special use case but, in general, I don't think it makes a lot of sense because:

1. Class properties ARE Case-sensitive by its nature (contrary to your statement in Ideas portal)
2. JSON fields ARE Case-sensitive by its nature (as per JSON standard)

REST code write the response to the current device.

An idea (to be tested) could be to intercept the calls in early stages, save the current device and change the current device to "some other device" (to be defined), then, after the code has finished, save the output to your log and switch to the "old" current device and write the output.

I think it can be done, it surely have some performance impact but...maybe feasible.

It has been very interesting and, as usual, keeping in touch with old fellows as well meeting new ones is the most valuable think of the conference.

And, HEY! only 10 month to the next conference!
Washington DC from 27th to 29th of April!

Please note that next conference will start with the Welcome Reception on Monday (usually Sunday).

I'm looking forward to meet you all in DC! 😊