Deprecated & replaced HttpRequestEndpoint__c fields with new HttpRequestEndpointAddress__c fields #773
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed #768 by deprecating the
HttpRequestEndpoint__c
fields onLogEntryEvent__e
andLogEntry__c
, and replaced them with newHttpRequestEndpointAddress__c
fields that have a much longer max length (2,000 vs 255).HttpRequestEndpoint__c
fields are now considered deprecated since they're not capable of storing the full value of long endpointsHttpRequestEndpoint__c
fields will continue to be populated for the time being, and the value is now auto-truncated to 255 characters to fix theSTRING_TOO_LONG
error that was reported in LogEntryEvent__e.HttpRequestEndpoint__c too short to store endpoint #768businessStatus
on the fields has been updated toDeprecateCandidate
inlineHelpText
on the fields has been update toDeprecated: instead use the field HttpRequestEndpointAddress__c
label
on the fields has been update toDEPRECATED: HTTP Request Endpoint
LogEntryRecordPage
flexipage to have bothHttpRequestEndpoint__c
(existing) andHttpRequestEndpointAddress__c
fieldsHttpRequestEndpoint__c
will be removedRelated context: this is essentially the same issue & solution used in release
v4.13.15
for the now-deprecated text(255) fieldsBrowserUrl__c
not being long enough, and they were replaced with new long textarea(2000) fieldBrowserAddress__c
(PR #720). It's probably worth reviewing all of the text fields in the data model (especially some of the older fields) to see if it would make sense to take the same approach for any other existing fields.