ThingWorx 9.3 grid with Fixed width columns and multi select exhibit unexpected behavior

[jensc]

Hello all,

I have some grids where all of my columns needs to be a fixed width.

The grid also needs to support multiple selections.

But when these two things are activated together, the grid has some (to me) unexpected behavior.

You can see that it cuts off part of the last column and creates a scrollbar at the bottom.

From what I can tell this is due to the fact that the grid part of the grid widget itself doesn't take into consideration the added column for the checkboxes.

Does anyone know of any workaround for this? Or maybe I am just doing something wrong?

Any help with this would be much appreciated as it is the last thing from my 9.1 -> 9.3 migration that I haven't been able to solve.

Thanks,

Jens

[bchaudhary]

Hello @jensc 

Could you pls share sample entities? I would like to try and test on my end.

Regards

Bhawna

[jensc]

Hello @bchaudhary 

Absolutely, here you go.

The entities has a tag "Application:MultiSelectGrid", so you might have to create this tag (or remove it from the xml) before importing it.

*Edit*

This is on version 9.3.5-b1258

Thanks,
Jens

[jensc]

Hello,

Did you have time to test this? 

I'm thinking if I should open a case for it or not as I can not really delay the go-live of the project much longer.

Thanks,

Jens

[OldGoat]

We've had a TON of headaches migrating our mashups to 9.3.5, including this one.  Tabs with grids in a pop-up were an exceptionally difficult issue.  I realize you may already have it this way, so please forgive me if I make a suggestion that you have already tried.  The example below was in a mashup, not a pop-up, but this fixed our issue similar to yours.  As an additional step, check for the "Margin" property on your widgets and enter "0 0 0 0" (the margin settings are Top, Right, Bottom, Left).  A singular "0" is supposed to be interpreted as 0 0 0 0, but it isn't always.

First place either a FieldSet or a FIXED size container in your mashup.  Next, drop a (or another) FieldSet in the container/FieldSet.  Finally, drop your grid in the fieldset.  It *SHOULD* clear up this problem...

[jensc]

Hello,

Thank you for your response.

I think my users could be OK with this issue for now, so I will table doing any mayor work arounds for now.

I did open a case with PTC and it seems like this is is due to a new issue in 9.3.5.

I got this from PTC support:

"Following some additional tests it turns out that this issue is new to Thingworx 9.3.5. The same is not reproducible in 9.3.4 and earlier. It is probably an unwanted side-effect of an implemented fix. I have reported this to R&D with all the information I could gather and I will let you know as soon as I receive a feedback."

I'll post here once again if I hear back from them regarding this though.

Thanks,

Jens

[jensc · Accepted solution]

Hello,

Finally found a fix to this issue.

It does require some custom CSS until they fix it in an upcoming release of thingworx.

Before:

Here is how to fix it for one grid:

Add this to your custom CSS:

.myGrid ptcs-grid::part(core-grid) {
      --vssbw: 33px !important;
}

Turn off linting (otherwise you are not allowed to set variables).

Set the CustomClass of your grid to "myGrid" and it should now look correct:

If you have multiple grids in one mashup that you face issues with, you can use this custom CSS instead:

@supports (ptcs-style-unit: "PTCS-GRID") {
    [part~=core-grid] {
        --vssbw: 33px !important;
    }
}

Thanks,

Jens