Changes to Agency Contact Info are not propagating from the existing system to Simpler

[mdragon]

Summary

A User shared that they had updated their phone number that they thought was associated with an Opportunity (357978) on January 2nd, but didn't see that change reflected on Simpler. It appears that is because when changes are made to fields like agency_phone_number it doesn't trip the is_opportunity_changed logic and as a result those changes are skipped over instead of being written through to the records in our database. This reflects in the logs: "Opportunity 357978 does not require an update for its current summary or status"

It seems like this might be because these fields exist on the summary, but changing them doesn't create a new current summary that replaces the existing one. I'm not sure this is actually the real problem as I dug deeper into the legacy and staging tables, I don't see the updated phone number there either. So something did cause us to check this Opportunity for changes, right around the time it was updated, but I'm not as sure that this is an issue fully on our side, or on our side at all if the data in the existing system might not reflect the change?

Reproducibility

I tried multiple times and saw the bug every time

How to reproduce the bug

Change agency contact info related fields on the opportunity_summary

Browser

None

Code of Conduct

• I agree to follow this project's Code of Conduct

[mdragon]

@chouinar I think we can mark this as closed per the investigation you did, correct?

[chouinar]

@mdragon - Yes, we just weren't sure during sprint planning if there were any other follow ups we might want to make