Horizantal scroll bar on Chart Straight table

[#1]

Currently we have a Chart Box with 20 columns expected to grow to 40-60 columns. The chart box allows us to specify the x and y position along with height and width. When the displayable values exceed those limits scroll bars appear on the horizontal and vertical.

Now we are trying to do the same with a Chart Straight Table as we need to be able to support the <url> capability. We have set the same x, y, width and height parameters. The options are also the same on the layout tab for both. However the Straight table does not create the horizontal scroll bar.

Is there an option somewhere we are missing?

[stevelord]

Hi, It's been awhile but I think I switched to the solution of putting the chart into a container object as a workaround after bumping into the behavior you described.  (Salvatore Zannino provided that answer.)  I never learned the root cause of the phenomenon, but container objects were a good workaround in my case since I had to make so many charts anyway.  (Software can be like that sometimes- you get a few solutions that should work and one solution that does work.   Root cause is probably something highly technical way in the background programming.)

[pooja_sn]

Hi Steve, I tried this and it allows me to set my straight tables size to fit to screen but it still does not show me a horizontal scrollbar so that I can scroll and see what all columns are there in my straight table.

Can you suggest if anything that I have missed..

[terrykavouras]

I came up with this solution too, but it only works when you are in WebView or viewing through AccessPoint - it doesn't work when in the design client.  When you are in the client, the container object has a limited scroll bar and won't scroll the whole width of a very wide table.

[terrykavouras]

There are a couple problems with using one (or limited) dimension and numerous expressions in a very wide straight table in order to get a horizontal scroll bar:

1. When a user makes a selection of an expression value, they are not truly selecting that value but rather are selecting the associated dimension(s).  This can lead to all sorts of confusion and unexpected behavior.
2. You can't enable drop-down select on expressions.  This could be an important aspect of having a wide table to begin with: the ability to show a user all manner of extra information and allow them to filter on it. But you can't do so with

My solution was to use a container object.  But be aware, that the full object scroll bar only appears when you are in WebView or viewing the app in a web browser.  In the design client, the scroll bar is limited.