catalog 18.104.22.168 ( i.e. catalog 17.1 with rollup1 patch applied )
A quick workaround for this issue is to give or set "Page Size" attribute of table with a value ( for example : 5 or 10 or default 50 , etc ) when having report data object populating table in a form.
In next cumulative patch , the engineering team will correct it . i.e it will not pop up that error message when "page size" attribute of the table is set as empty and table is using report data object . However , we recommend you to set the "Page Size" attribute of table with specific value when you want to use report data object to populate the table so that to avoid the performance issue relating to it , especially when the table is populated with large amount of data via report data object