Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] Bad Message 414 reason: URI Too Long using virtual ExternalId

See original GitHub issue

Describe the bug Configured a virtual ExternalId. While executing it throws a URI Too Long error.

To Reproduce Create a significantly long virtual ExternalId like

SBQQ__Quote__r.SBQQ__Account__r.IntegrationId__c;SBQQ__Quote__r.SBQQ__Key__c;SBQQ__Product__r.FullSegmentsNumber__c;Quant__c;UOM__c;SBQQ__Quote__r.IncoTerms2__c;CurrencyIsoCode

Expected behavior No error

export.json export.json.txt

Log file 2020-09-14__23_05_37.log

Issue Analytics

State:
Created 3 years ago
Comments:7

Top GitHub Comments

1reaction

hknokhcommented, Sep 15, 2020

This case need to debug on your side…

0reactions

hknokhcommented, Sep 15, 2020

Need to see the constructed query and how it handles this

Top Results From Across the Web

Bad Message 414 reason: URI Too Long

The receiving server is rejecting your URL saying it is too long. When you need to send large amounts of data, you have...

414 URI Too Long - HTTP - MDN Web Docs

The HTTP 414 URI Too Long response status code indicates that the URI requested by the client is longer than the server is...

Receiving the 'Bad Message 414' error message when trying ...

The reason you are getting the above error is: The receiving server is rejecting your URL saying it is too long. When you...

Errors | ngrok documentation

When something goes wrong with ngrok, we report a unique error code. Each error code points to a specific location in our codebase...

Cisco Webex Contact Center Analyzer User Guide

Column Name Description Field or Measure Data Ty... Agent ID A string that identifies an agent. Field String Agent Session ID A string that identifies...