Paging in the grid creates the problem

RE: Paging in the grid creates the problem

Peter Lewis — Mon, 08 Jun 2020 16:04:14 GMT

Good point, the tostring() I have in my example above would always concatenate with semicolons, so joinarray() might be better if you want to separate with a comma or something else.

RE: Paging in the grid creates the problem

davel001150 — Mon, 08 Jun 2020 16:00:02 GMT

Peter Lewis is stating basically exactly what I was about to say.

I'll just add that you may be able to get by with a simple joinArray() function, which you will want to do with a convenient separator to make sure your list converted to a string still looks like a list of items to your end users. You can add spaces in your separator as well, so you can make the formatting real nice.

Whichever method is easiest. There's no wrong answers among the things that make the pink box stop.

RE: Paging in the grid creates the problem

Peter Lewis — Mon, 08 Jun 2020 15:17:00 GMT

I think the issue is with the country column, since that contains a list of lists. I'd suggest updating your expression to cast the full list of countries for the given row to a single string like this:

a!gridTextColumn(
  label: resource("Country"),
  field: "country",
  data: a!forEach(
    items: local!datasubset,
    expression: tostring(
      index(
        fv!item,
        "country",
        ""
      )
    )
  )
)

It's actually decently rare to need many nested a!forEach() functions, so usually there is a simpler solution rather than having to nest all of those together so many times!