Long Request URL causes the 400 Bad Request - Known Error

Long Request URL causes the 400 Bad Request Description If there are too many filters are defined in a record in Report Source table, then users are not able to see these filters when they open the record. They see 400 (Bad Request) on browser console logs.

Steps to Reproduce

Navigate Reports --> Report Source 2.Right click on the list header and then click on the import XML 3.Click on the Choose File and choose xml which is attached on the problem. 4.Click the upload button. 5.Open the record "Test Filters" in report source table

Actual Behavior: Users see the 400 Bad request on browser console error and they can't see the filters. (153 filters are defined in that record) Expecter Behavior: User should be able to see and update the filters in that particular record. Workaround This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In the field to determine whether any versions have a permanent fix.