I have two repeat grids in two places, one on the home screen of the application and is a worklist, and the other in a work object that displays a list of accounts contained within the request. Both leverage the same skin rule and have identical layout properties (save for the data source). Within the skin rule I’ve established a single breakpoint and set the responsiveness behavior to “Transform to list”. However, one grid responds correctly while the other does not.

The repeating grid that works is for a user’s worklist, and when the responsive breakpoint hits, I see the following list behavior:

• Primary Value
  • Secondary Label               Secondary Value
  • Secondary Label               Secondary Value
  • Secondary Label               Secondary Value
• Primary Value
  • Secondary Label               Secondary Value
  • Secondary Label               Secondary Value
  • Secondary Label               Secondary Value

The repeating grid that doesn’t work is for a list of accounts contained within a work object. When the responsive breakpoint hits, I see the following behavior:

• Primary Value                       Secondary Label   Secondary Value Secondary Label   Secondary Value
• Primary Value                       Secondary Label   Secondary Value Secondary Label   Secondary Value

For some reason, all of the secondary columns stay as columns, and on the same row as the primary column, as if it partially transformed into a list. Just for fun I moved the working grid onto the same section as the broken grid, which then displayed the same incorrect behavior when in that section.

I know the skin is shared as I can update various values and see the changes on both grids.

Is there some setting on the section, harness, or flow action that could be breaking the responsiveness for grid layouts?

Any help would be appreciated.