@MaxonL16591286 You can use ＠LengthOfPageList（）in the visibility condition of the Add row(add item) button.

exp

＠LengthOfPageList（.YourPageList）< maximum count

This way , the "Add" action will only be visible until the list reaches the maximum .

@MaxonL16591286

Add a simple guard plus a server-side check. 1) Decide your cap (e.g., 10) and store it in a setting/param/property. 2) In the table (page list) toolbar, make Add row visible/enabled only when @(Pega-RULES:Utilities).SizeOfPageList(.YourList) < .MaxRows. 3) If you use row add via a custom button, call a data transform/when that blocks the add and shows a message when the cap is reached. 4) Add a Validate rule on submit that checks SizeOfPageList(.YourList) > .MaxRows and sets a page message like “You can add up to X items.” 5) For safety, run the same check in a pre-processing data transform (or activity) before save to catch bulk adds/imports. 6) Optionally hide the Add icon entirely once the limit is hit using a When rule on the column toolbar. 7) If users can delete, re-enable Add when the size drops below the cap. 8) Keep the limit as a DSS/setting so you can change it without a deploy.