search

progressivetech / net.ourpowerbase.sumfields

The Summary Fields extension creates read-only custom data fields that extend Contact and are automatically populated with up-to-date totals such as total lifetime contributions, last contribution amount, last attended event, etc.
Other
8 stars 29 forks source link

triggers settings not enabled #83

Closed twomice closed 3 years ago

twomice commented 3 years ago

As described at https://civicrm.stackexchange.com/q/35581/907

I'm seeing similar behavior to that reported in the SE question above. Summary Fields configuration page reports this, even after rebuilding triggers with civicrm/menu/rebuild&reset=1&triggerRebuild=1 sK1gl

This seems to indicate that triggers are not in place, and therefore real-time update of configured summary fields will not be happening, even though the cron job may be doing periodic updates.

jmcclelland commented 3 years ago

Are you running the latest release or the latest version in github? If you are not running the latest version in github - would you mind upgrading and letting me know if that fixes the probe?

I also did more of a follow up on the SE question here: https://civicrm.stackexchange.com/questions/35581/summary-fields-triggers-settings-not-enabled/38613#38613

The SE answer provides a work-around and some helpful user info on how to debug. But... if you find that upgrading to the github version automatically solves the problem then I'll definitely release a new version.

andyburnsco commented 3 years ago

I'm on version 5.0.0 and did the steps described here https://civicrm.stackexchange.com/questions/35581/summary-fields-triggers-settings-not-enabled/38613#38613. The "Status of current settings" and "Data update method: Cron Job" are now correct but no triggers exist for civicrm_contribution or Triggers for civicrm_participant.

image

The Scheduled job says e.g. Finished execution of Call SumFields.Gendata API with result: Success (a:1:{i:0;s:89:"Original Status: scheduled:2021-04-23 06:32:07, New Status: scheduled:2021-04-23 07:47:03";}) image

Separately, what are the findings of this extension on a large db of around 800K records? I've been very selective and using the simplified fields for performance considerations.

jmcclelland commented 3 years ago

Hi @andyburnsco - you have a choice of update methods - either "Instantly" or "When the cron job runs"

If you choose "Instantly", then triggers will be added and the second a new contribution is added to your database, the triggers will update the summary fields.

However, you seem to have chosen to run on the cron job - which is why the triggers are not enabled, so that's to be expected.

As for the performance question, if you mean 800K contributions, it should be fine. If you mean 800K contacts, then it's more then I have any real experience with!

jmcclelland commented 3 years ago

I'm going to close this as fixed, but please let me know if there are still any outstanding aspects to the issue.