First stop, try holding the shift key and clicking the browser refresh button. This recaches the page and fixes weird stuff sometimes.

Next stop, when did this start happening? Has anything changed recently, like an upgrade, new customization, etc?

Sorry Daryl, should’ve mentioned in original post I tried the usual suspects, clearing cache, different browsers, etc.

When: unsure. I don’t work w/ sales orders and mostly do report designer/GIs. I just asked someone in Customer Service and they said about two years, lol!

I will ask our main dev who deals with our VAR. Currently the workaround in customer service is to use column filters. I just tested in Sales Orders and Purchase Orders and they both behave as expected… even a simple string that should return a lot of results only takes 2-3 seconds. Sales Order Lines will sit there for 45-60 seconds.

Is this on a custom generic inquiry, or what screen ID? Perhaps there is simply too many results. Could you try changing the GI to limit to the past year’s worth of orders or something?

GIOZ3255

Sales Orders are about 21000 records and searches are almost instantaneous. Sales Order Lines are about 41000 and it hangs for close to a minute.

I duplicated the GI and changed the default display 100 records to 35 and it didn’t make a difference.

Looking in the results grid there are 56 columns, and 6 of the columns have VisibleExpr like

“=iif( =SOLine.RequestDate] < SOShipLine.ShipDate] , 'Late' , 'On Time')”

So I’m not sure if the number of columns plus a handful of visibility expressions would cause it to crawl with 41000 records.

By comparison, Sales Order has 35 columns with no visibility expressions and half the records.

Try disabling those conditional value columns.

Will do. I also just noticed this:

Looks like I might need to re-do the relationships?

I doubt that's the issue, but you could disable that too.

Yeah, those pop up occasionally but never noticed a negative impact.

Disabling the visibility conditions made an instant improvement. That’s not the solution I wanted because CS will not want to turn those off, lol. But at least I know. Thanks Daryl!

You could try doing conditional formatting instead. Keep the values as actual fields, but if an order is 'late', turn it red.

Ahhhh dude, that is a big brain moment. yes, hadn’t thought of that! I wish I could like your comment twice!

Haha, just an idea. If it works, I can't tell you why that's faster, cuz it seems like it would be doing all the same processing.