Forum Discussion
TylerParker
8 years agoQrew Assistant Captain
Matthew,
Our stops are automatically recorded by a device that is plugged into the engine, transmits that data to a server, and then imported into our QuickBase through an API call at the end of the day. So every record is going to be present at once. The stops are numbered, so perhaps option #1 could work if based off that order. I'm also interested in hearing more about option #2 if you have the time, because it sounds like a good way to keep routes separate. Thanks!
Our stops are automatically recorded by a device that is plugged into the engine, transmits that data to a server, and then imported into our QuickBase through an API call at the end of the day. So every record is going to be present at once. The stops are numbered, so perhaps option #1 could work if based off that order. I'm also interested in hearing more about option #2 if you have the time, because it sounds like a good way to keep routes separate. Thanks!
- MCFNeil8 years agoQrew CaptainWhat are the chances those 'logs' have any unique identifier AND they are somewhat sequential in their uniqueness?
If so that would be amazing, and somewhat simple to implement.
If not, you would need some type of script to that will sort and write the previous stop values in.
A skilled programmer could do it in about 2-3 hours - MCFNeil8 years agoQrew CaptainNative option: If you want to make a mess of summary fields and lookup fields... You could make stacking summary/lookup fields (my worst nightmare).
Stop 1, (minimum stop time for the Route)
>then send as a look up
Route - Stop 1,
>Then Stack
Stop 2 (minimum stop that is greater than "Route - Stop 1"
> Then send as a lookup
>Repeat for x number of possible stops.
Thats just the beginning:
Now you need to calculate the previous stop on the same record.
It would be a huge mess of conditional evaluations....
if stop 2, then use stop 1 to stop 2,
if stop 3, then use stop 2 to stop 3,
x repeats. - TylerParker8 years agoQrew Assistant CaptainUnfortunately they don't have completely unique identifiers from one individual record to another. I think the script to sort stops by driver/vehicle and then write the values sequentially, low->high, based on "time of stop" is a great idea. You're right, the second option seems like a nightmare!
- MCFNeil8 years agoQrew CaptainLet me know if you want to get a more in depth look. Or you can have one of your guys take a crack at it.
mneil@mcftech.com