Near Intersection of I-35 & I-90 Southern Mn. | The question came up yesterday concerning field boundaries and if they are "brought along" when an agsetup file is used to transfer a field to another Ag Leader display.
After further investigation I found that if the "original" has a Boundary and AB lines associated with it, they do "come along" when agsetup is used to copy to another device.
Had I done things in a different order, I could have saved myself some work but it worked out OK. I used the agsetup files on the "new" fields which were actually old fields with new names. There were no boundaries and AB lines associated with the new names so after an agsetup transfer, the new names on the receiving device did not have Boundaries or AB lines.
Had I copied the appropriate and good AB lines from the old field names to the new field names on the first display and THEN used the agsetup file procedure, I would have accomplished my goal with less interaction.
The thing to remember is that doing a backup from one display (always a good idea) and then using it to restore to another display will in effect delete what had been on the second display and completely replace it with what is on the first display. In other words, for the most part the second is no identical to the first. Sometimes that is desirable.
Using an Agsetup file copies information from the first display and when placed in the second display can add to what was already there. If there are conflicts such as the same name etc., the procedure will ask you what to do about this. The Agsetup process does not delete anything from the second display but may add to it. Sometimes this is the desired result.
Edited by tedbear 2/8/2026 07:39
|
Naming fields architecture for future SMS use
