Bad Request error 400 - Advanced Find

Posted By jford_1 over 7 years ago

Our users are getting Http 400 Bad Request error when using Advanced Find. The Advanced Find screen comes up populated with data from the stored find; however, after modifying the selection parameters and executing a new "find" they get the Bad Request error. I have been able to replicate on Chrome, IE and Edge. I have cleared all cookies. I have restarted IIS and Tomcat. Dashboard and stored reports are working fine. Just seems to be occuring with Advanced Find (but could be elsewhere since we are not power users). Any suggestions?

0 jcbaker over 7 years ago

Anyone else experiencing this issue? We have many Saved Advanced Finds but I can't edit or delete them because it comes up with "Bad Request". On CRM7.3 SP1.1 now, didn't see reference to this particular problem in the release notes for either SP2 or SP3... any suggestions would be appreciated.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 huwf over 7 years ago

Do you get any errors in your SQL logs at the same time?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 TJC_1 over 7 years ago

Same with us. We keep on getting an HTTP 400 Bad Request Errror while using Advanced Find. Any solutions to fix this problem?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Sage CRM Team over 7 years ago

Hi there

This issue is resolved in Sage CRM 2107 R2 which is due for release at the beginning of April.

Thanks

Emma
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Sage CRM

Bad Request error 400 - Advanced Find

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING