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.

[Mohit_Gupta]

Hi @thomaskennedy ,

Can you please check the scenario for the first 20 rows if it's working or not and try to put some integer number in properties so that in future you can use maximum number.
You can refer the below link to check the properties:
https://docs.servicenow.com/bundle/vancouver-application-development/page/administer/decision-table/...

Please mark helpful if works

Thanks

Mohit

[thomaskennedy]

I tried setting the max_questions to a number higher than the number of questions I hve defined. This had no effect on the observed behavior.

[Dr Atul G- LNG]

Hi @thomaskennedy 

Very wired idea, try cache.do and then try. 

else HI support is only way.

[Martin27]

Hi @thomaskennedy ,

I´m experiencing the same issue. I have created 200 questions via API and the first 20 records are not showing the display names. Did you get any reply from ServiceNow support?

It looks like this is just a "displaying" issue, as I´m still able to get decisions even from those "invisible" rows 🙂 Although speed could be better. when running in script (using API) it takes something around a second to get an answer 🙂