Have you ever looked at a record and thought, “Why is this field set to that value? I didn’t update it.” With Apex code running in the background, it can be tricky to track down the real source of a field update.
HappySoup makes this easier with Read vs Write indicators for Apex classes. When a field is referenced by Apex, HappySoup shows whether the class is:
Writing to the field (updating or setting the value)
Reading from the field (checking or using the value)
If a class is marked as write, that means it can directly set or change the field’s value. This is a strong clue that the class might be responsible for unexpected values appearing in your data.
If a class is marked as read, it only uses the field’s value as input. These classes are not the source of the change, so you can rule them out if you’re investigating why a field value keeps getting updated.
Different ways to use it
Troubleshooting data changes: Find which class is writing into a field when you see unexpected values.
Auditing automations: Identify which Apex classes are able to read a field, for example when you’re checking compliance or security requirements.
Impact analysis: Understand not just where a field is referenced, but how it’s being used, so you can plan safer changes.