Read through the below post, now closed. One quick question, if the NS cant control the size of the output, can it control the number or width of the columns? there is plenty of room to make this NS show as 4 or maybe even 5 columns, which would then allow all the data to be shown before it runs off the bottom. 

An obvious question which you have probably thought through, but I didnt see it covered in the post, so thought I would ask. 

Thanks! sorry to hear people are having trouble with Eisy NS like this one. 

 

 

49 minutes ago, dbwarner5 said:

Read through the below post, now closed. One quick question, if the NS cant control the size of the output, can it control the number or width of the columns? there is plenty of room to make this NS show as 4 or maybe even 5 columns, which would then allow all the data to be shown before it runs off the bottom. 

An obvious question which you have probably thought through, but I didnt see it covered in the post, so thought I would ask. 

No, it can't.  The admin console has full control over how the content is rendered. The node server (via PG3(x)) simply sends the value (numeric value).  

The only control the node server has is over values that are represented with text.  The node server creates the numeric value to text mapping that the admin console uses.