Forum Discussion
BlakeHarrison
5 years agoQrew Captain
It sounds like you may want to increase the complexity of your application structure so that you would end up with fewer fields to have to consider in any calculations. As a start, I would encourage you to build tables for your Departments, Classes, and Phases, creating records in each of them for the associated data. These would end up driving drop-downs in the other tables I'd recommend - Job Departments, Job Classes, and Job Phases. These would be setup in a relationship structure similar to what I've outlined below:
------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quick Base Solution Provider
Atlanta GA
404.800.1702 / http://datablender.io/
------------------------------
If your Job Cost is based on calculating the total cost for everything at the lowest level, you can just have the Cost field on the Job Phase table and do a summary field all the way up to the Job to get your total. If you're calculating that Job Cost based on other factors such as Wage and Time, you could put those fields on the Job Phase table and the Job Cost could become a simple formula of [Wage]*[Time]
------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quick Base Solution Provider
Atlanta GA
404.800.1702 / http://datablender.io/
------------------------------
AlexBennett3
5 years agoQrew Trainee
I'll look into the suggestions!
Thanks for your help Blake!
------------------------------
Alex Bennett
------------------------------
Thanks for your help Blake!
------------------------------
Alex Bennett
------------------------------