v4.12.4 - Bugfix: Child Log__c Records Not Properly Linked to Parent Log__c Records #607
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 @ctcforce for reporting this bug!
Core Unlocked Package Changes
Logger
Apex Class ChangesResolved LogHandler not linking child logs correctly #585 (reported by @ctcforce) by updating
LogHandler
to handle some scenarios where aLog__c
record would have a value inParentLogTransactionId__c
but anull
value inParentLog__c
. Now in anAFTER_INSERT
context,LogHandler
requeries any potentially orphaned childLog__c
records and links them to their parentLog__c
records. Please note that this does not fix any existing problematic data in your org - it only prevents new problematic records from being created. To fix existing data in an org, you can run this anonymous Apex script:Installation Info
Core Unlocked Package - no namespace
Full Changelog: v4.12.3...v4.12.4
sf package install --wait 20 --security-type AdminsOnly --package 04t5Y000001Mk5KQAS
sfdx force:package:install --wait 20 --securitytype AdminsOnly --package 04t5Y000001Mk5KQAS
This discussion was created from the release Bugfix: Child Log__c Records Not Properly Linked to Parent Log__c Records.
Beta Was this translation helpful? Give feedback.
All reactions