Hi Uwe, You're absolutely right, thanks for sticking with it! The original version only stripped commas (,) assuming US-style formatting, but didn’t account for European locales where a dot (.) is used as the thousands separator (like 1.620). So the parsing failed silently when it hit the dot. I’ve just finished a patched version that makes the parsing locale-safe, it now handles both 1,620 and 1.620, as well as formats with spaces like 1 620. You can download the updated version here: 👉 https://github.com/smart4solutions/apex_ir_pagination/releases/tag/1.0.1 Please give it a try in your preprod environment, I’d love to hear if that clears it up! CU, Jordy

Hi Uwe, Nice progress already, great that the plugin UI is showing up! If it’s displaying "1 - 1 of 1" in the dropdown, one thing worth checking: what does the original APEX pagination label (the one hidden by the plugin, inside .a-IRR-pagination-label) show? The plugin reads from that native element, so if it's already showing "1 - 1 of 1", then the issue likely isn't with the plugin, but with the report itself returning fewer rows than expected. Could be a difference in filters, session state, or query logic between environments? Curious what you find! Sounds like you're getting close. CU, Jordy

Hi Uwe, Thanks again for the kind words, great to hear it’s working in dev! Just to confirm a few things to help narrow it down: Are you using the plugin from GitHub in preprod too? And was the page exported from dev, or did you set it up separately by installing the plugin and recreating the Dynamic Action? If it was the latter, missing or misconfigured DA could explain why it only partly works. Also, check if the pagination text (X - Y of Z) is visible, since that’s required for the plugin to attach. If the script is loaded, you should see debug output in the console that confirms whether the right div is targeted. Let me know what you find, happy to take a look with you! CU, Jordy