Tweet
Quite simply ... a calculated field type which takes its value by totalling another numeric field in a sub-entity, without having to write any code.
(Obviously, there could be multiple fields in the sub-entity to sub-total ... e.g. number of hours, cost per hour, etc.
Plus the field(s) being sub-totalled could themselves be calculated fields).
Example situations:
Project Header entity ... Task sub-entity
Account entity ... Lifetime purchases sub-entity
Invoice Header entity ... Invoice line items sub-entity
etc.
The sub-totalling/calculation could take place by a button-action (e.g. "RE-CALCULATE") on the parent entity record or just when the parent record is saved.
Therefore, the data entry process would be:
1. Enter the required number of sub-entity records (e.g. all the tasks that make up a project).
2. Click on the button on the parent entity screen to re-total and update from the required sub-entity values.
The attached dummy screen shot shows approximately what the field setup page would look like.
(Obviously, there could be multiple fields in the sub-entity to sub-total ... e.g. number of hours, cost per hour, etc.
Plus the field(s) being sub-totalled could themselves be calculated fields).
Example situations:
Project Header entity ... Task sub-entity
Account entity ... Lifetime purchases sub-entity
Invoice Header entity ... Invoice line items sub-entity
etc.
The sub-totalling/calculation could take place by a button-action (e.g. "RE-CALCULATE") on the parent entity record or just when the parent record is saved.
Therefore, the data entry process would be:
1. Enter the required number of sub-entity records (e.g. all the tasks that make up a project).
2. Click on the button on the parent entity screen to re-total and update from the required sub-entity values.
The attached dummy screen shot shows approximately what the field setup page would look like.
Attached Files