Can we extend the record count function execution time?

Hi @Michael Hansen 

How many records you will get in the GI?

As @Naveen Boga mentioned we can see 10million records in GI,

Generally the error comes because of Incoorect GI relations

1. One way to optimize a Primary List is by reducing the number of fields that have "Use in quick search" enabled (highlighted)

2. Check the tables in the GI, if there are any that are not necessary we recommend removing them (obsolete tables)

   TO=o calculate the count and display the results, the system needs to run two queries. To ensure the responsiveness of the application, the Generic Inquiry system will wait for a predetermined amount of time (a few seconds). If the count of records is not returned in the allotted time, the query is canceled and the GI will only display the records.

   More than likely, this means that the GI has a complex join expression or condition that requires full table scans instead of faster-clustered index operations. '

3. Analysis of the SQL Query Execution plan through SQL Management Studio is recommended in such cases. In some cases, it can simply be because you’re missing a field in the relationship (ex: joining by OrderNbr instead of OrderType, OrderNbr).

4. One way to optimize a Primary List is by reducing the number of fields that have "Use in quick search" enabled 

5. Check the tables in the GI, if there are any that are not necessary we recommend removing them (obsolete tables)

6. Another suggestion would be to enter a value for the "export top" field if the client is not exporting all the values and the first few only

THANK YOU @VladSushkin83 

@manikantad18 - I will look into killing the quick filter toggles on the inquiries!