Fairfield County, Ohio, USA | I have experienced this before. I *think* I have figured out that it happens when some event -- doesn't even have to be the same type of operation -- is for field A while in or near field B.
For example, we were at Field A, which happened to not exist in InCommand yet (because I forgot to create it). My brother needed to get to the run screen to change a sprayer parameter to get it to agitate (long story), so... he picked Field B, because it was the first GFF combination. I don't even think that the tractor moved while that field was selected, because I couldn't see anything logged. But I then closed that event, created the correct Field A, started a new event with it, and he got to work. It logged properly.
But then later, after he started doing things in Field B, I couldn't see any activity at all in AgFiniti under Field B. If I switched to Field A, then I could see the things that he did in Field A and Field B, of any operation that he had done in both places.
I think that Ag Leader needs to overhaul how they handle building maps. They seem to be leaning into spatial sorting rather than being strict with GFF selections. I can understand that, if boundaries were strictly required, but they're not. |
Agleader AgFiniti help needed
