Best practice recommendations on "Save all objects to the server "

[Aravindkumarj]

Hello!

Are there any best practice recommendations on when to use the option "Save all objects to server"? Our Enable Now has several thousands of objects. Each time an author is onboarded, we suggest that person to first sync all objects from the server which eventually times out and after they are done editing or recording a simulation we suggest that they use "Save all objects to server". Again they can never do this successfully since it times out. We have maintained a higher value for the server timeout but that doesn't help. So we were wondering if there were any best practice recommendations on saving the changes back to the server. I feel like we are overloading the sync process by saving everything everytime. Any suggestions for us?

Thanks.

[ShaneLipke]

Hi Aravind,

This KBA provides a solution to your issue with synchronization timeout.  My only advice is to set the value of each of the Registry Entries to approximately 480000 instead of 120000, as listed in the KBA.  You will need to restart your PC after implementing the Registry Entries to see the change.

Outside that, my personal preference is to only download the content structure when synchronizing large Workspaces.  Turn on the Check out folder structure only field when using the Workspace > Check Out Objects functionality.

If you have the folder structure in Producer, just right click a folder that contains content that you want to work on and select Server Bulk Actions > Update All Objects from Server.  This will allow you to download the content for that folder, rather than the entire Workspace.

Regards
Shane

[BartRhoten]

This issue happens a lot with offshore workers, especially those using VPN. The VPN adds its own lag, so you want to avoid VPN whenever you can. Additional tricks are to use an ethernet cable instead of WiFi to connect your PC to your network router, and pay for the fastest internet connection you can afford.

[Aravindkumarj]

Thank you! Good tips. We will try that.