By default %ToJSON method prints empty properties.

If you pass pFormat without "e" flags (that is passed by default), then empty properties are skipped:

USER>set p = ##class(%ZEN.proxyObject).%New()
 
USER>set p.a = 1
 
USER>set p.b = 2
 
USER>do p.%ToJSON()
{
        "a":1,
        "b":2
}
USER>set p.b = ""
 
USER>do p.%ToJSON()
{
        "a":1,
        "b":""
}
USER>do p.%ToJSON(,"alotw")
{
        "a":1
}

I encourage you to use Caché 2016.1 with native JSON support. Don't start with %ZEN.proxyObject. See great article by Stefan Wittman about JSON support in 2016.1: https://community.intersystems.com/post/introducing-new-json-capabilities-cach%C3%A9-20161

Why do you need this?

For example, for debugging purposes you might use second argument of Get method:

do request.Get(,1)

In that case "instead of connecting to a remote machine httprequest will just output what it would have send to the web server to the current device".

The first time a message is added to a domain by $$$Text, $$$SessionLanguage is used: http://docs.intersystems.com/cache20152/csp/docbook/DocBook.UI.Page.cls?KEY=GCSP_localization#GCSP_C199107

$$$SessionLanguage is determined by locale of current process, that is by default is the same as locale of Caché instance http://docs.intersystems.com/cache20152/csp/docbook/DocBook.UI.Page.cls?KEY=GSTU_customize#GSTU_customize_nls

Default locale for Caché instance is determined during installation based on OS locale. For example, on English Windows that has Russian in Regional Settings, Caché is installed with locale rusw (ruw8 for 8-bit installation). You can change locale after installation. There is no option to select locale during installation.

You can change current session language with ##class(%MessageDictionary).SetSessionLanguage("ru")

Hi Dan.

I don't know of ways to have up-to-date Age as dimension.

You can have level property Age, that will be calculated at run-time (checkbox "Get value at runtime").

See for example, HomeD.City level, property Population at Patients cube in SAMPLES namespace.

Also, see "Defining Age Members" section in docs: http://docs.intersystems.com/cache20152/csp/docbook/DocBook.UI.Page.cls?KEY=D2MODEL_ch_calc#D2MODEL_calc_member_recipes_age_members

Hi Chip.

You can brand userportal per namespace

You can override branding in each particular dashboard.

I think the only way to have different branding for different logins for the same dashboard is to create new class that inherits from Dashboard viewer and assign properties companyName, companyLogo, companyStyle manually based on login