Is there a limit to the row count in a Decision table?

[thomaskennedy]

When the number of rows in my decision table reaches about 180, it stops displaying the condition for the first 20 rows. Here, row 20's Condition column is suddenly empty, while 21 and every row thereafter appears normal.

If I open row 20 in the decision rule view its condition appears OK.

Max_inputs and max_questions are both empty.

I don't see how this actually harmful, as these rows will never be edited going forward, but it looks really odd.

[thomaskennedy]

Martin,

I don't know that I opened a support incident about this. I checked that my API is unaffected, shrugged, and moved on. I just put 20 dummy rows in at the top. The way I'm using the table is to read it all in up front and put everything in a map. That's ok for my very simple requirement, where I ask questions like "Is string x a partial match on any key in the map?". If performance is poor I would not notice because I'm using the map, not the DT.