v4.12.6 - Bugfix: Added automatic string truncation for LogEntryEvent__e fields #612
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 @TrangOul, @BastienRaoul, and @Damecek for reporting these issues!
Core Unlocked Package Changes
Automatic String Field Truncation for
LogEntryEvent__e
Platform Event RecordsLoggerDataStore.EventBus
to support usingDatabase.DmlOptions
for enabling automatic field truncation on platform events, using some custom truncation logic (platform events do not normally support usingDatabase.DmlOptions
).Logger
now passes an instance ofDatabase.DmlOptions
withAllowFieldTruncation == true
when publishingLogEntryEvent__e
recordsData Masking Optimizations
LogEntryEventBuilder
to automatically truncate any provided String parameters before callingapplyDataMaskRules()
. This truncation is somewhat redundant with the string truncation now performed inLoggerDataStore
- but the use of data masking on certain String parameters necessitates an initial truncation before any other parsing occurstruncateFieldValue()
inLogEntryEventBuilder
, now thatLoggerDataStore
will automatically truncate platform event string fieldsInstallation Info
Core Unlocked Package - no namespace
Full Changelog: v4.12.5...v4.12.6
sf package install --wait 20 --security-type AdminsOnly --package 04t5Y000001Mk5UQAS
sfdx force:package:install --wait 20 --securitytype AdminsOnly --package 04t5Y000001Mk5UQAS
This discussion was created from the release Bugfix: Added automatic string truncation for LogEntryEvent__e fields.
Beta Was this translation helpful? Give feedback.
All reactions