Tabatha, Darshan –
Can you tell me what further information you want about our workflow? As I've said, in attempting to prevent (warn) users against some incidence of possible ?folder? corruption... you've created another anxiety in our usage of Sync. The users encountering this took (by all accounts unnecessary heroic measures to avoid the reported possibility of corruption (resyncing TrimbleSysQue Palettes, taking HOURS)
Question(s):
- Why would you concentrate on MANUAL Syncs to do this "Duplicate path checking"? Wouldn't actually scheduled (timed) sync jobs be more of a risk?
- What are the various use cases for TCS? Do you know people are using it for syncing Trimble SysQue .XML files?
- Wording of the terms is unintuitive, and part of the issue – with the
- top level being a Project (right?),
- the next level termed "Schedules" (even though a MANUAL sync isn't really a schedule at all)
- corruption of the FOLDER structure – or of the FILES?
- Why would you (apparently) not check for the other Sync "Schedules" being OPPOSITE (one upload, one download) – rather than this nebulous warning?
I'm trying to work through your logic for this warning and wanting to understand where prior corruption occurred. I'm also working through a rewording of the warning in case you don't modify the underlying logic.
The SYNC path specified [actual path here] is used in another Project Sync Schedule. Running multiple sync schedules to the same path MAY result in corruption of the data or folder structure. Please confirm Sync setup including Sync direction (Upload vs. Download) before proceeding.
Do you still want to continue with this Sync?
Gary Foote
gary@since1928.com
C 775 | 771 7644
Dedicated RapidResponse IT support for
Savage & Son VDC | Sage Accounting
garyf@savageandson.com
