If you have Auditing turned on, you can check your audit log for login failures in system management portal. That will tell you why the login failed, which might point you in the right direction.

Does the test user account have the right security resources to access the database you're trying to log into? The quick easy way to check if you have a security-related issue is to give the test user the %All role and see if the issue goes away. If it does, you need to figure out what resource/role is missing for the user account. You don't want to permanently leave the %All role on there.

Yes. You can use a variable name starting with ^, like ^MyGlobal, and it will be a global. You will not be able to access it via SQL, but you will be able to see it with the globals in the system management portal. You can also reference globals in a different namespace by using ^|"namespace"|MyGlobal.

It might be nice to make such tracking conditional. Like "Log all queries that take over 10 seconds to run" or whatever number is appropriate for your usage.

The only places I know of are, if it caused an xDBC error, that in the system management portal under System Operation, System Logs, xDBC Error Logs, and if it was a query run through the management portal itself, you'd be looking in the global %sqlcq and for your search mask, use %sqlcq("NAMESPACE","SMPQueryHistory","USERNAME" to see the query history for a specific user. That's where the query history you see in the SQL section of the management portal is stored.

I don't know of anything overall, though.

All we can tell from this is that in the class gen.Custom.HS.Model.OEOrdItem.TabularTextResultsEMR, you have a method called GetData, and on line 872 of the .1 file for that class, you have a variable named rs that is undefined.

Page not found, or Invalid Action? If it's page not found, how is the web application configured?

@Enrico Parisi , with Global Masters, we get a few points for having an answer marked as correct on the community. People often only mark the first correct answer they see. So if the user who posted the question didn't see this thread before the AI bot's post appeared, it's somewhat likely that the bot's post will be marked as the correct answer even though a human user answered the question first. That's all. Seems just a little unfair to me.

@DC AI Bot 
When I checked on this post earlier today, Vitaliy's correct answer was here, but the AI Bot's was not. Now it's showing here as if the AI Bot's answer was first. That is troublesome, particularly if Vitaliy is a Global Masters user.

The specific issue here is probably that when you tried to set text = type.%Get("text"), the variable "type" wasn't an object because it didn't exist or wasn't a dynamic object/array within the original object. You might want to try:

set iter = identifiers.%GetIterator()
     while iter.%GetNext(.key, .value, .type ) {
        set type = value.%Get("type")
        if $ISOBJECT(type){
            set text = type.%Get("text")
        }
        else{
            set text = ""
            //Or whatever you wanted to do if type wasn't an object.
        }

Maikel, if your variable is named var in your ObjectScript code, then you would use where xyz = :var in the embedded query. The colon marks that this is a host variable.  

You can set this up using your routine mappings. You can have each namespace have a different database for its globals but share a database for the routines. Then they'll all have their own data, but be running off of the same code.

I only have back to Cache 2018, not 2017, but can you try:

set myproc = ##class(%SYS.ProcessQuery).%OpenId($J)
if myproc.ClientExecutableName = "CSTUDIO.EXE"{
    //You are in Cache Studio
}
else{
    //You are not in Cache Studio
}

I'm not totally clear on what you're trying to do, but I have a feeling you might want to replace "quit" with "return status". Inside a catch block, a quit command will quit just the catch block and code execution will continue after it. Replacing that with return status would make the code execution stop right there, returning the error.

Here's my small but useful contribution:

Add an "Add Server to VS Code" Option to System Tray Icon

Calling the methods this way is effective for testing the methods, yes. You just want to get really familiar with the %CSP.Request class. This approach isn't a good way to troubleshoot issues with your routes, or with authentication, though, as it bypasses those steps. For that, you'd probably have to define %request appropriately, then call some of the methods your API inherits from %CSP.REST, but I'm not as familiar with those.

And in addition to all of that, one of the workarounds people seem to like using is to have things comma-separated and enclosed in " to make sure it's getting the right commas, but I'm working on ERP software for the millwork industry in America. We're still allergic to metric here, and we use " to mean inches and ' to mean feet, so we can't use those either!