If you create hour or dollar attributes at the activity (appointment) level you can sum these up at the project / phases level. Remember, however, that the activity for a project can be filtered by class and type, so if you just sum across the ProjectActivity relationship, your totals will change with your filters--this can be a good or a bad thing.

To make this explicit, sum across both the ProjectActivity relationship (which respects the filters) and the ProjectActivitySimple relationship (which does not). In the screen shot below, the top fields sum ProjectActivity, the bottom fields sum ProjectActivitySimple.

Enjoy!

Can you show me how you would add these fields to the activities table?

jimrecht wrote:Can you show me how you would add these fields to the activities table?

Sure. (Sorry for the delay in responding to you!)

The fields you see in the portal (Hours reg. 8 ot. 1.5) are just two new fields in the appointments table. Lets call them ApptHoursReg and ApptHoursOT. These are just number fields that contain or calculate the number of hours spend on the activity / appointment.

Then below the portal we have four totals. These are calc fields in the Projects table. The first row calculates the total "shown" in the portal and will change to respect the portal's filter criteria. These calcs would be defined as:

Sum ( ProjectActivity:: ApptHoursReg ) and Sum ( ProjectActivity:: ApptHoursOT )

Both calcs are defined to return the type number and evaluate from the context of Project. The lower row of totals does not respect the project's activity filters and will always show the total reg and ot hours. These fields are also calcs defined in the projects table and are defined as

Sum ( ProjectActivitySimple:: ApptHoursReg ) and Sum ( ProjectActivitySimple:: ApptHoursOT )

Here as well, both calcs are defined to return the type number and evaluate from the context of Project.

Hope that helps.