You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bugSomething isn't workinglogger engineItems related to the core logging engineunlocked packageIssues and enhancements that specifically apply to the unlocked packagescenario-based loggingItems related to Logger.setScenario(), LoggerScenarioRule__mdt, etc.
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Thanks to @rcastanosgonzalez for reporting and fixing this bug!
Core Unlocked Package Changes
setScenario()
to properly (and always) set the scenario on each log entry. Previously, the value was often incorrectly set tonull
Installation Info
Core Unlocked Package - no namespace
Full Changelog: v4.13.6...v4.13.7
sf package install --wait 20 --security-type AdminsOnly --package 04t5Y000001MkHRQA0
sfdx force:package:install --wait 20 --securitytype AdminsOnly --package 04t5Y000001MkHRQA0
This discussion was created from the release Fixed setScenario() function in logger LWC.
Beta Was this translation helpful? Give feedback.
All reactions