Reports with date parameters don't paginate #5179

Open
opened 2026-02-20 16:30:59 -05:00 by deekerman · 4 comments
Owner

Originally created by @MaxSantolo on GitHub (Mar 19, 2024).

After the creation of a report with date parameters (like from - to) and using "value" as parameter so that the user can enter a specific date, and after adding a main grouping of the report based on a "feedback field": if one of the groups has more than 20 items clicking the paging results in empty group.

Expected Behavior

Pagination should show the next 20 group results.

Actual Behavior

Pagination shows empty list and disables pagination buttons.

Steps to Reproduce

  1. Create a report with "from" and "to" value of date parameters
  2. Group the report based on another field ("status" for example)
  3. Choose the dates and activate the report: no pagination

Context

I need a report of leads grouped by feedback in a period of parametric dates (from - to)

Your Environment

  • SuiteCRM Version used: 8.5
  • Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Chrome and Firefox
  • Environment name and version (e.g. MySQL, PHP 7): PHP 8.1, MariaDb
  • Operating System and version (e.g Ubuntu 16.04): Debian 11
Originally created by @MaxSantolo on GitHub (Mar 19, 2024). After the creation of a report with date parameters (like from - to) and using "value" as parameter so that the user can enter a specific date, and after adding a main grouping of the report based on a "feedback field": if one of the groups has more than 20 items clicking the paging results in empty group. #### Expected Behavior Pagination should show the next 20 group results. #### Actual Behavior Pagination shows empty list and disables pagination buttons. #### Steps to Reproduce 1. Create a report with "from" and "to" value of date parameters 2. Group the report based on another field ("status" for example) 3. Choose the dates and activate the report: no pagination #### Context I need a report of leads grouped by feedback in a period of parametric dates (from - to) #### Your Environment <!--- Include as many relevant details about the environment you experienced the bug in --> * SuiteCRM Version used: 8.5 * Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Chrome and Firefox * Environment name and version (e.g. MySQL, PHP 7): PHP 8.1, MariaDb * Operating System and version (e.g Ubuntu 16.04): Debian 11
Author
Owner

@serhiisamko091184 commented on GitHub (Mar 20, 2024):

Hello @MaxSantolo,

thanks for raising the issue,

I'm afraid I'm unable to replicate that behavior,

would you please be more specific about the report setting and add some screenshots if possible (particularly fields used and conditions applied)?

I'd like to clarify as well about modules - is it only the case for the Leads module or several modules?

Thanks in advance!

Regards,
Serhii

@serhiisamko091184 commented on GitHub (Mar 20, 2024): Hello @MaxSantolo, thanks for raising the issue, I'm afraid I'm unable to replicate that behavior, would you please be more specific about the report setting and add some screenshots if possible (particularly fields used and conditions applied)? I'd like to clarify as well about modules - is it only the case for the Leads module or several modules? Thanks in advance! Regards, Serhii
Author
Owner

@MaxSantolo commented on GitHub (Mar 21, 2024):

@serhiisamko091184
Modules Impacted are leads and contacts.

Screenshot 2024-03-21 alle 08 57 34
Screenshot 2024-03-21 alle 08 57 21

Search
Screenshot 2024-03-21 alle 08 58 58

After Next Page click
Screenshot 2024-03-21 alle 08 59 11

@MaxSantolo commented on GitHub (Mar 21, 2024): @serhiisamko091184 Modules Impacted are leads and contacts. ![Screenshot 2024-03-21 alle 08 57 34](https://github.com/salesagility/SuiteCRM-Core/assets/45451159/1bff5e62-c03b-4a70-ba81-45ba656e5bde) ![Screenshot 2024-03-21 alle 08 57 21](https://github.com/salesagility/SuiteCRM-Core/assets/45451159/d03b4c63-d1a6-4965-bcd8-70a49cfdc288) Search ![Screenshot 2024-03-21 alle 08 58 58](https://github.com/salesagility/SuiteCRM-Core/assets/45451159/67ae289e-2dda-4218-8a59-13c45fe682e3) After Next Page click ![Screenshot 2024-03-21 alle 08 59 11](https://github.com/salesagility/SuiteCRM-Core/assets/45451159/bbdbcb5d-8cbd-4a27-a3bc-3172fadfa528)
Author
Owner

@serhiisamko091184 commented on GitHub (Mar 22, 2024):

Hello @MaxSantolo,

thank you for your quick response,

the issue has been moved to the SuiteCRM repo as present in v.7 as well.

I was not able to achieve the same behavior from the very first time, because having this set of local settings works fine for me:
image

One more time thanks for bringing this up to our attention!

Regards,
Serhii

@serhiisamko091184 commented on GitHub (Mar 22, 2024): Hello @MaxSantolo, thank you for your quick response, the issue has been moved to the SuiteCRM repo as present in v.7 as well. I was not able to achieve the same behavior from the very first time, because having this set of local settings works fine for me: ![image](https://github.com/salesagility/SuiteCRM/assets/116086008/3aa81e47-363f-4217-a05d-a1e227e52b52) One more time thanks for bringing this up to our attention! Regards, Serhii
Author
Owner

@MaxSantolo commented on GitHub (Mar 22, 2024):

Hello @serhiisamko091184,
I can confirm It's a problem of date format. With mm/dd/yyyy works perfectly. Probably something in the js.
Let me know if I can help in any way.
Regards,
Max

@MaxSantolo commented on GitHub (Mar 22, 2024): Hello @serhiisamko091184, I can confirm It's a problem of date format. With mm/dd/yyyy works perfectly. Probably something in the js. Let me know if I can help in any way. Regards, Max
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/SuiteCRM-SuiteCRM#5179
No description provided.