Hi @Elath De Silva, If the customer code is almost the same as TQA then you could report this to RnD.
If it is a bug they will correct it. If it is a limitation or a huge modification then they might go for future developments (For that, best option would be to create an idea so you can track it your self)..
Hi @Elath De Silva
Could you please check the bug fix 153684 and see whether it resolve the issue or not?
Best Regards,
@Elath De Silva
There are many reasons for a performance issue in a window. Mainly this is observed in customer environments due to the high volume of data, code issues or index fragmentation.
The best option is to report it to RnD after filling the performance checklist.
This checklist will also let you check the indexes on the affiliated table. Once RnD checks on it they will come up with a solution by optimizing the code.
Regards,
Nadeesh
Hi @Elath De Silva ,
investigate the issue using the profiler and get the performance killer statement .
then compare the exact code part with the core version and take care of it accordingly .
(either apply a bug that you find or create a check list and report it to RND)
in this situation best option is to use a profiler .
Here is an article on using a profiler in IEE
How to get profiler report via debug console | IFS Community
if the situation is more severe , as in the application times out or gets freeze up use the divide and conquer method fused withthe autonomous table .
Investigating performance of application freezers and crashes | IFS Community
Hi Elath,
Would be best to report it to RND with info on the following:
- activity_tab
- project_connection_tab
- project_connection_parent_tab
- project_connection_details_tab
- project_connection_revenue_tab
- project_baseline_detail_tab
- 1) The total number of records in each table
- 2) The indexes available in each table
A possible solution suggested would be to:
Changed how data is retrieved from the PROJECT_CONNECTIONS_OVERVIEW view which is connected to the Project Connections overview window. It now no longer refers to the project_connection_parent_tab table.
refer to solution 293935 for more details on a similar issue.