Repository navigation
v4.11.10 - Dynamic field visibility for LogEntry__c HTTP response header fields #573
jongpie
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Core Unlocked Package Changes
New
LogEntry__ccheckbox fieldsLogEntry__cfor each long textarea fields that didn't previously have an equivalent checkbox field. Note: these new fields will be inaccurate for existingLogEntry__crecords (but correct on new records).HasDatabaseResultJson__c- set based onlogEntry.DatabaseResultJson__c != nullHasHttpRequestBody__c- set based onlogEntry.HttpRequestBody__c != nullHasHttpResponseBody__c- set based onlogEntry.HttpResponseBody__c != nullHasHttpResponseHeaderKeys__c- set based onlogEntry.HttpResponseHeaderKeys__c != nullHasHttpResponseHeaders__c- set based onlogEntry.HttpResponseHeaders__c != nullLogEntryHandler_Teststo be true unit tests that do not rely on DMLDynamic field visibility for
LogEntry__cHTTP response header fieldLogEntryRecordPage.flexipage-meta.xmlto have conditional visibility for the fieldsHttpResponseHeaderKeys__candHttpResponseHeaders__c, based on the new checkbox fieldHasHttpResponseHeaders__cInstallation Info
Core Unlocked Package - no namespace
Full Changelog: v4.11.9...v4.11.10
sf package install --wait 20 --security-type AdminsOnly --package 04t5Y000001OigxQACsfdx force:package:install --wait 20 --securitytype AdminsOnly --package 04t5Y000001OigxQACThis discussion was created from the release Dynamic field visibility for LogEntry__c HTTP response header fields .
All reactions