New post
AllAccepted answers
Robert Cemper · Feb 5, 2018

as all values out of your SQL query come from server you should be able
to setup the content of title on server side as you do for other ZEN components.

#; compopse titel .... into variable mytitle
   set %page.%GetComponentById("Priority").title=mytitle
  


There is  a wide doc on programming ZEN pages
http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GZEN

Robert Cemper · Feb 5, 2018

Basically $c(1) s a NONPRINTING character - it has to be invisible by definition.

Instead of WRITE command use ZWRITE to visualize it or $TRANSLATE function to make it visible.

example:

USER>s ^rcc=$lts($lb(123,"abc",23432,"hak","uuk"),$c(1))
 
USER>w ^rcc
123abc23432hakuuk
USER>zw ^rcc
^rcc="123"_$c(1)_"abc"_$c(1)_"23432"_$c(1)_"hak"_$c(1)_"uuk"
USER>ZZDUMP ^rcc
0000: 31 32 33 01 61 62 63 01 32 33 34 33 32 01 68 61         123.abc.23432.ha
0010: 6B 01 75 75 6B                                          k.uuk
USER>write $TR(^rcc,$c(1),"*")
123*abc*23432*hak*uuk
USER>
Robert Cemper · Feb 2, 2018

property onselectrow as %ZEN.Datatype.eventHandler;

onselectrow event handler: This event is fired when a new row is selected. This event is passed a variable, which, which indicates how the row was selected: "", "click" or "keypress".

I'd assume in your case as you did neither "click" nor "keypress"    var which ="" will apply.

So you may use this to ignore the call and return without action.

Robert Cemper · Feb 2, 2018

It would be easier to help you with the concrete call  to ZAUTHENTICATE in hands.

In addition ZAUTHENTICATE.mac needs to be modeled by un-commenting  lines.

Or do you use the pre-configured OAUTH2.AUTHENTICATE.mac

in both cases you need to have activated this line:

Set Properties("Comment")="....whatever you may pass along...."

according to your description this is done .

So the issue might result from the way the call is done
Comment in ZAUTHENICATE.mac Line 90 says:

Properties - Array of returned values, passed by reference

So your call should look like

 Do ^ZAUTHENTICATE(ServiceName,Namespace,Username,Password,Credentials,.Properties)
#;--------------------------------------------------------------------^^^


 It's the dot in front of variable name Properties that does the Pass by Reference and enables you to use the updated array after the call.

The dirty approach would be to name your array %myProp instead of Properties thus using a variable with public scope.

Robert Cemper · Feb 2, 2018

Pls. be more specific on "It is not working."
+ what would you expect to work
eventually you have code and data separated, then it's more than just a single DB
various mapping may add even more DBs

You should get previous releases from WRC based on your service contract.
But be aware: from 2007 to 2017 there have been  15..20 releases.   
Each with changes + release notes that may affect you.  

Robert Cemper · Feb 2, 2018

Hi Ben,

I just installed a few samples as in description . CONGRATULATIONS !
- not only that I get what I want and leave the rest aside
- I also can split samples by subjects in several DBs and namespaces without being trapped by (hidden) dependencies.

I think this makes live for training and teaching significantly easier!
And allows central bug fixing independent from core release dates.


A great idea! Thanks!

Robert Cemper · Feb 2, 2018

To my understanding the main purpose of introducing %INLIST in our SQL was
to have a more handy option than the classic IN (....)

%INLIST takes a Single $LISTBUILD()  as parameter with a Variable number of values that you pass at runtime by only 1 "?"

while IN (p1,p2,p3,p4)   or better IN (?,?,?,?)  requires a fixed static number of parameters during execution. 
so you have to know the maximum number of values ahead when you create your query
and eventually to fill unused parameters by some impossible value to feed the query