Tracking Historical Status Changes
Hi! I want to be able to track status' for orders, arrivals, updates of orders as they change. This is how I have things set up right now:
I didn't only want to have the input on the rig...
Forum Discussion
Hi Annie,
One way people track historical data to make import/export and reporting on status changes even easier is to create a child table to track those status changes. Then you can create a Pipeline that is set up for every time a Status changes create a record in the new Status Changes Tracking child table to reflect that change (you can even set it up to capture other data as well if you need). This way you have a separate table of status changes that you can report on and track to figure out things like how often your status is updated to problematic in a time frame across all projects etc. You can even then put a report link to that child table on your current table so you can see them all.
------------------------------
Evan Martinez
------------------------------
One way people track historical data to make import/export and reporting on status changes even easier is to create a child table to track those status changes. Then you can create a Pipeline that is set up for every time a Status changes create a record in the new Status Changes Tracking child table to reflect that change (you can even set it up to capture other data as well if you need). This way you have a separate table of status changes that you can report on and track to figure out things like how often your status is updated to problematic in a time frame across all projects etc. You can even then put a report link to that child table on your current table so you can see them all.
------------------------------
Evan Martinez
------------------------------
Can you expand on this a little more? I have a field that is call "STATUS" . In that I have a drop down with
Do I need another table to do this?
------------------------------
Tina Revermann
------------------------------
- Contract
- Details
- Available
- Completed
- Billing
- Final Costing
- Closed
Do I need another table to do this?
------------------------------
Tina Revermann
------------------------------
- You question is a classic one that difficult. I think that the best suggestion is to have a Pipeline or Automation which writes out a record to a child table with the Status and the Start Date/Time. But the first step of that Automation would be to scan for any existing Status Log records that were not closed out with an End Date/Time.
Then write out a new Status Log record. The Start date/ time can actually come from either the date Created field or else a field set to default to the Current Date Time.
The advantage of this logging method is that status changes can go backwards in the sequence. You can then make a summary report as an embedded Report Link on the main Parent record of the total time by Status.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------I am trying to build a table that takes the "change of status" as input and then add the days mentioned to move to another phase. I want to record the time stamp when someone enters the phase + number of days to complete that or get out of that phase, which will be the due date. If someone fails to update the phase or misses the due date, it will show the number of overdue days and turn red. How can I do that on QuickBase without pipelines as I do not have access to create pipelines??
------------------------------
Chaitali Damani
------------------------------Can you clarify a little bit? It sounds like you're wanting to have someone enter some kind of update that would capture the current timestamp, and then they would enter a number that is a a new expectation for when they would finish/exit that stage? That number input + timestamp is now the new expectation that the phase is expected to end/due?
If yes, then your simplest solution without pipelines would be to have a new table that:
- User adds a record that is related to the Phase in question where phases have many 'updates'
- Add a snapshot field that when you create the update it snapshots the current due date of the phase
- In the update, enter a duration field for the number of days
- Calculate snapshot field of current due date + duration is your new due date
- Summary the new date date into the Phase and that is the Due Date that you'd be referencing.
Please feel free to correct any gaps though in my understanding of your request.
------------------------------
Chayce Duncan
------------------------------
