Forum Discussion

AlexBennett3's avatar
AlexBennett3
Qrew Trainee
5 years ago

Historical info for line chart.

Hey Everyone, 

I wanted to see If I could get some input on some options for QuickBase, so that I can change my code to accommodate these new data points. 

I have a Line Chart that displays a jobs info, 5 points creating a line to show 'Job Budget', and 'Budgeted Hours' where these 5 data points are for each phase of the job then just connecting a line between them. Then I have another single dot on the chart to show where the job is 'Currently' based on actual costs and actual hours worked.

I'm trying to see if there is a way for QuickBase to take a "Snapshot" every Friday of where the Job is at, and then I can write the code to include this, that way over time I can show that line compared to the Budget to see how far we are off budget. 

My issue is I don't know how to do this without having a bunch of records created to be able to pull those fields over to the custom code page... any thoughts from anyone on if QuickBase has something I can do to snapshot these numbers each week and be able to include in my code without a million stored? 

Thanks,
Alex

------------------------------
Alex Bennett
------------------------------
  • If you want to see change over time, you will have to capture that historical data in another table and build the reports on that table.

    ------------------------------
    Blake Harrison
    bharrison@datablender.io
    DataBlender - Quickbase Solution Provider
    Atlanta GA
    404.800.1702 / http://datablender.io/
    ------------------------------
    • AlexBennett3's avatar
      AlexBennett3
      Qrew Trainee
      But from my understanding, I'll have to have a record for every point of data to display on my Custom Coded Line Chart correct? I just don't see any other way. For example, if I want to get a weekly current for that job to display on the code, I'd need a field to reference from for the code. So if I have 50+ jobs, each going from 3 months to 5 years in length, I'd end up having a million records created to be able to display that data?

      ------------------------------
      Alex Bennett
      ------------------------------
      • MarkShnier__You's avatar
        MarkShnier__You
        Icon for Qrew Legend rankQrew Legend
        You would need a record created for each weekly snapshot.  An Automaton would run a saved Table to table copy each weekend to copy the jobs into the History table. But you would only copy a few fields that you need for the charts and they can be children of the job, so you don't need to copy any fields that can be looked up, like [Job Name].

        ------------------------------
        Mark Shnier (YQC)
        Quick Base Solution Provider
        Your Quick Base Coach
        http://QuickBaseCoach.com
        mark.shnier@gmail.com
        ------------------------------