Report Module Ignores 'reportable: false' Setting #5314

Open
opened 2026-02-20 16:59:32 -05:00 by deekerman · 1 comment
Owner

Originally created by @desarrollador20 on GitHub (Apr 7, 2025).

Issue

Despite Adding 'reportable: false' to an AOS_Invoices Field to Exclude It from the Reports Module (via public/legacy/custom/modules/AOS_Invoices/Ext/Vardefs/vardefs.ext.php), It Still Appears as a Selectable Field

Possible Fix

In the file public/legacy/modules/AOW_WorkFlow/aow_utils.php, add the following inside the foreach loop:


![Image](https://github.com/user-attachments/assets/af0a8a75-efb3-43f6-ba33-ac005d1d749c)

if (isset($_GET['module']) && $_GET['module'] == 'AOR_Reports' && isset($arr['reportable']) && $arr['reportable'] === false) {
    continue;
}

This change ensures that the field has the reportable property and considers the originating module, as this function is used not only for reports but also for workflows.

Steps to Reproduce the Issue

1) Add the property **reportable: false** to a field in **AOS_Invoices**.  
2) Attempt to include that field from the **Reports** module.

Context

Not all fields must appear to be used in reports

Version

8.8.0

What browser are you currently using?

Chrome

Browser Version

Chrome - Version 131.0.6778.264 (Official Build) (64-bit)

Environment Information

PHP 8.3.17

Operating System and Version

Ubuntu 22.04.4 LTS

Originally created by @desarrollador20 on GitHub (Apr 7, 2025). ### Issue Despite Adding 'reportable: false' to an AOS_Invoices Field to Exclude It from the Reports Module (via public/legacy/custom/modules/AOS_Invoices/Ext/Vardefs/vardefs.ext.php), It Still Appears as a Selectable Field ### Possible Fix In the file public/legacy/modules/AOW_WorkFlow/aow_utils.php, add the following inside the foreach loop: ``` ![Image](https://github.com/user-attachments/assets/af0a8a75-efb3-43f6-ba33-ac005d1d749c) if (isset($_GET['module']) && $_GET['module'] == 'AOR_Reports' && isset($arr['reportable']) && $arr['reportable'] === false) { continue; } ``` This change ensures that the field has the reportable property and considers the originating module, as this function is used not only for reports but also for workflows. ### Steps to Reproduce the Issue ```bash 1) Add the property **reportable: false** to a field in **AOS_Invoices**. 2) Attempt to include that field from the **Reports** module. ``` ### Context Not all fields must appear to be used in reports ### Version 8.8.0 ### What browser are you currently using? Chrome ### Browser Version Chrome - Version 131.0.6778.264 (Official Build) (64-bit) ### Environment Information PHP 8.3.17 ### Operating System and Version Ubuntu 22.04.4 LTS
Author
Owner

@johnM2401 commented on GitHub (Apr 14, 2025):

Hey!

Thank you for raising this issue.

Just to let you know, I've transferred this over to the SuiteCRM7 repo as I was able to replicate this on SuiteCRM 7.14.6
Meaning that, as this functionality is legacy-based, any fixes to this done on the SuiteCRM7 repo should then be pulled into the subsequent SuiteCRM8 release.

Thank you again!

@johnM2401 commented on GitHub (Apr 14, 2025): Hey! Thank you for raising this issue. Just to let you know, I've transferred this over to the SuiteCRM7 repo as I was able to replicate this on SuiteCRM 7.14.6 Meaning that, as this functionality is legacy-based, any fixes to this done on the SuiteCRM7 repo should then be pulled into the subsequent SuiteCRM8 release. Thank you again!
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#5314
No description provided.