Which (if any) logic hooks fire when a report is run?

[tobydz]

I'm implementing some new code that sets a date on a module record based on the newest note created on that record. Doing a "Mass Update" isn't an option for me (long story, short ending), so, if there's a logic hook that will fire when I run the report to pull those values, that would save me from "touching" each file to populate this date field.

Would 'after_retrieve' or 'process_record' fire off during a report query?

Thoughts? Suggestions?

[tobydz]

So far I've tested both 'process_record' and 'after_retrieve'.... neither of them seem to fire off when running a report.....

[andopes]

There is no logic hook loaded at Report context.

[christianknoll]

Sugar does not fire hooks on loading a report. You can use our KINAMU Reporter to achieve what you are looking for. In our Reporter (also in the free basic edition) )you can create a KReporter field which is a non db field you can use to e.g. run a subquery in the report.

One of our customer is doing a similar task with this where they run a report on accounts and then have defined one field that shows the last date of either a call, meeting or email that was sent to that account. This is purely evaluated at the report runtime and thus a clean and safe approach.

Alternatively you can also embed custom functions or even custom php code on the report that gets evaluated before the output is processed if you need logic to be performed past the SQL.

christian.

I'm implementing some new code that sets a date on a module record based on the newest note created on that record. Doing a "Mass Update" isn't an option for me (long story, short ending), so, if there's a logic hook that will fire when I run the report to pull those values, that would save me from "touching" each file to populate this date field.

Would 'after_retrieve' or 'process_record' fire off during a report query?

Thoughts? Suggestions?

[tobydz]

There is no logic hook loaded at Report context.

Yeah so I guess my workaround is going to be using the process_record hook (which fires off in list views) and just page through the records to perform the updates. I know it's dirty, but at least this way it'll get my new code to kick in *before* the reports are run.