-
Error while loading default custom view.
We can see that in any production order when we click on BOM view and filter it and saved the view and pin it as default view in the system, and then when we open it again it will throw an error “The view query has been overridden because of a conflict.”
This issue occurring on multiple grids. example:
all production orders > production order (Tab) > production details > BOM view
"The view query has been overridden because of a conflict."
-
We would like the ability to select more than one project to update status from the All-Projects List/form
We need the ability to perform bulk updates on project statuses within the project list form. Specifically, there is a requirement to select and edit multiple projects simultaneously, such as changing the status of several projects from "created" to "in process" efficiently. This functionality is essential for managing project workflows effectively.
-
Ability to Bulk update the Benefit Limit amount for employee/worker
The feature in Benefit elements > Plans > Payroll details tab > Default deduction limits allow setting a benefit limit amount. However, if the limit amount is changed in the future, it does not apply to employees/workers already enrolled in the benefit; they continue to use the old limit. We would like to request functionality that enables bulk updating of the limit amount for all employees/workers.
For instance, if a user has 100 workers enrolled in Benefit A and wishes to set a limit amount for all workers/employee, they will require the capability to bulk update the limit amount for all workers/employee simultaneously.
-
Managing the bankreconciliationhistorydetails Table
We propose an enhancement to the current data management capabilities within the bank reconciliation module. We need for more granular control over historical data, specifically the ability to remove subsets of data from the bankreconciliationhistorydetails table once it is deemed no longer necessary for reconciliation purposes.
The Following needs make this feature be considered for implementation:
The primary concern is the indefinite growth of this table, which leads to increased storage costs for data that is outdated and no longer required. The ability to selectively archive and delete data would provide All Users with the flexibility to manage their storage more efficiently and cost-effectively.
Allow for the safe deletion of data from the bankreconciliationhistorydetails table without affecting the integrity of ongoing or future reconciliation processes.
This enhancement would not only optimize the performance of the bank reconciliation module but also align with best practices for data lifecycle management, ultimately benefiting the customers by reducing unnecessary storage overhead.