v4.13.15 - Deprecated & replaced BrowserUrl__c fields with new BrowserAddress__c fields #721
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
-
Thanks to @Ben-Nathan-CTM for reporting this bug!
Core Unlocked Package Changes
This release fixes #696 by making a couple of changes to how the browser's address is captured when logging in lightning components
ComponentLogger
to auto-truncate JS browser fields (includingLogEntryEvent__c.BrowserUrl__c
)public
propertyComponentLogger.ComponentLogEntry.browserUrl
is now deprecated & will be deleted in a future release. It's only intended to be used internally by Nebula Logger, so this hopefully doesn't impact anyone - but mentioning it here, just in case 😉BrowserUrl__c
onLogEntryEvent__e
andLogEntry__c
with new long textarea (2000) fieldsBrowserAddress__c
BrowserUrl__c
fields are too short to store some long URLs (such as URLs with a lot of parameters), and the existing fields can't be converted from text(255) to long text area fields, so new fields are neededBrowserUrl__c
fields will still be populated for foreseeable future (with a truncated value), but they are now considered deprecated - any references in reports, list views, queries, etc. should be updated to use the newBrowserAddress__c
fieldsLogEntryEvent__e
andLogEntry__c
Installation Info
Core Unlocked Package - no namespace
Full Changelog: v4.13.14...v4.13.15
sf package install --wait 20 --security-type AdminsOnly --package 04t5Y0000015oF5QAI
sfdx force:package:install --wait 20 --securitytype AdminsOnly --package 04t5Y0000015oF5QAI
This discussion was created from the release Deprecated & replaced BrowserUrl__c fields with new BrowserAddress__c fields.
Beta Was this translation helpful? Give feedback.
All reactions