Back in June, I updated the campaign dashboard view to annotate related objects with a canonical_uuid field in order correctly handle relationships.
More recently, we added a canonical_uuid property directly to the Change model. It seems that these two changes are conflicting and throwing the following error when trying to access any related data filtered through the CampaignDetailView._filter_latest_changes method: property 'canonical_uuid' of 'Change' object has no setter.
I'm not 100% sure where that error is occurring yet, but changing the annotated field name allows us to get the distinct related objects that we want, while still using the property within templates to access the canonical record. I'm going to deploy this as a temporary fix and we can re-evaluate the filtering after to see if there's a better way to handle this.
Back in June, I updated the campaign dashboard view to annotate related objects with a
canonical_uuidfield in order correctly handle relationships.More recently, we added a
canonical_uuidproperty directly to theChangemodel. It seems that these two changes are conflicting and throwing the following error when trying to access any related data filtered through theCampaignDetailView._filter_latest_changesmethod:property 'canonical_uuid' of 'Change' object has no setter.I'm not 100% sure where that error is occurring yet, but changing the annotated field name allows us to get the distinct related objects that we want, while still using the property within templates to access the canonical record. I'm going to deploy this as a temporary fix and we can re-evaluate the filtering after to see if there's a better way to handle this.