Hidden column in a grid

Kaan Cetinturk
Kaan Cetinturk
in AppWorks #1

Hello all, 

 

I have a grid on my form that links to a Business Object. When I set a column of the grid as "hidden", the next column also gets hidden.  Have you also experienced this before? If I set all columns as read-only, the grid works fine...

 

I work on BPM 9.0.3 HF1

 

Thanks,

 

Kaan

Tagged:

Comments

  • Jerome_Pearce
    Jerome_Pearce
    #2

    It appears to be a problem with IE8. If you set the width to zero, this is an effective 'e-workaround'.

  • Scott_Leclerc
    Scott_Leclerc
    #3

    You can also place all hidden columns to the right end of the grid.

  • Kaan Cetinturk
    Kaan Cetinturk
    #4

     

    That's what I thought originally, but it is not the best practice. Most of the time you need the ID column to be hidden and you refer to this column somewhere else in the code, like User.Input[0]. If you put this column at the end, every time you add a new column, you need to change your code.

     

    Do you know if this is identified as a defect or should I create a service request?

    Thanks,

     

    Kaan

    Scott wrote:
    You can also place all hidden columns to the right end of the grid.

     

     

  • Jerome_Pearce
    Jerome_Pearce
    #5

     

    Kaan wrote:

     

    That's what I thought originally, but it is not the best practice. Most of the time you need the ID column to be hidden and you refer to this column somewhere else in the code, like User.Input[0]. If you put this column at the end, every time you add a new column, you need to change your code.

     

    Do you know if this is identified as a defect or should I create a service request?

    Thanks,

     

    Kaan

    Scott wrote:
    You can also place all hidden columns to the right end of the grid.

     

     

    Could not agree more.

     

     

    I have posted it here before, and it was reconised, but I would report it formaly as well.

  • Kaan Cetinturk
    Kaan Cetinturk
    #6

    I just created an SR. I will keepyou updated...

  • Joe Smith
    Joe Smith
    #7

    This was already logged in our tracking system as DEF15723.

  • achopra
    achopra
    #8

    In version 9, User.Input[n] no longer refers to the column ordering in the grid, but rather to the order of the variables as defined in the underlying business object that is being used in the grid.  Thus, it shouldn't matter what order you put the columns in the grid, and you could put the hidden columns at the end if need be...not having to worry about changing code if the grid layout changes.  This is a big benefit of having the User.Input[] not being tied to the UI layout.

  • Jerome_Pearce
    Jerome_Pearce
    #9

    Good point, Ari - I had forgotton about that!

     

    We use standard scripts to add folder ids & sequence numbers in the first two columns of a grid (at least until we get SQL Server Identity fields and default values for grid columns) so we are forced to do this at the start to make ir standard, but unless you do something like this, the order does not matter.

  • Grzegorz Lag
    Grzegorz Lag
    #10

    Hello
    This bug seems to exist still in version 9.1.2.1.
    When do you plan to fix this?

    Is there any plan to make some extension to processcontext.userinput, to have column names instead of index.

  • Toby Miller
    Toby Miller
    #11

    In IE, if you add your metastorm sites to the Compatibility View Settings the grids will format correctly.

     

    Open IE. 

    In the File menu click Tools.

    Select Compatibilty View Settings

    Add your metastorm sites.

Categories

image
OpenText CE Products
AppWorks
Gateway & Platform