If this is just for occasional troubleshooting what is wrong with retrieving the files from a sample device via Remote Control?

With just two file-sync rules,  you can temporarily disable the file-sync rule you don't want to waste bandwidth before you initiate "sync file now" and have that file-sync rule re-enabled afterwards.

It is for occasional troubleshooting, but with the number of devices and customers (and the nature of our app) it's fairly frequent and we have a 24/7 support center.  They currently do retrieve it with remote control, but I was looking for a way to help automate that to facilitate troubleshooting especially if we could get a whole group of device's files in one click versus connecting one at a time with remote control.  That's the way we always did it with Pocket Controller but it's slow and cumbersome at best when managing a mass of devices.

In theory I could certainly disable one rule to have only the other one active, but that's not going to be a feasible scalable long-term solution.  Like I mentioned, we have a 24/7/365 call center for supporting our application on these devices so there's no way I could manage disabling/enabling the rules based on when a call were to come in based on which file the personnel was trying to get. 

I'd like to have the option to select which rule to sync, but it doesn't look like that's going to be possible.  I was hoping it could be done via script.  It looks like I may have to come up with a different method.

You could create FileSynRules on VirtualGroups and set them to "Sync on Device addition".

2 Groups for Each rule.

Then when you need the logs you drop the device in the specific filesyncgroup and the files get synced right away.

Virtual Groups will get us what we need.  Thanks!

I have created 2 virtual groups, underneath a regular device group.  I have created 2 file sync rules, each attached to one of those virtual groups.  (EX.  File Sync A targets Virtual Group A;  File Sync B targets Virtual Group B). 

When I drag a device into Virtual Group A, it syncs the correct file per File Sync A.  I then delete the device from Virtual Group A and check that it doesn't have any current rules assigned to it.  I think drag that same device into Virtual Group B, and it syncs the file per File Sync B, but it also does a sync for other file in File Sync A also.  Do I need to have these under a Virtual Root Group or something?  I've never utilized Virtual Groups before so I'm not sure if I did something wrong or not.  The logs are below.  You can see it was added to a virtual group, file sync rule was processed, device was deleted from virtual group, added to other virtual group, and both file sync rules were processed.  I have sanitized these logs a bit.

Hi,

under Device Configuration Tab you can check if both rules are still applied.

What Version are you using?

14.3 and 14.4 are behaving as they should

We are running 13.4.  When I remove the device from the virtual group, the rules assigned tab does not show the old rule anymore.

I created a new virtual root group as a test and put both of the virtual groups with the file sync rules attached underneath that, but same issue persists. 

I did another test where I moved a device into the group, did a file sync and confirmed the file, deleted the file back on the server since it's set to only sync if file is different, deleted the device from the virtual group, and request a file sync on the device, and both files were synced to the server from each file sync rule.  Device was only located in it's real group at that time with no file sync rules applied to it.

It seems as though once a device gets put in a virtual group, the file sync rule(s) remain persistent even once it is deleted from the virtual group.

After reading through some release notes, I found this below.  Guess that explains it.  I'll see if I can update to a higher maintenance release to resolve this issue.  Will report back once complete.