Navigate to GoSyncMobileConfiguration.xml on your GO! Sync Mobile GIS Server. This can be found at C:\GISDataServer\MobileDownloads\Default\MobileConfiguration (where C:\ is the root directory, and Default is the client configuration group the tool needs to be available to).

Open the file in a text editor such as Notepad++ and locate the ‘Toolbars’ section.  Under ‘File Management Tools’ there may be an existing entry for a ‘Printing’ tool with caption ‘Print Current Map’.  Remove comment tags to enable tool and save file.

If this entry does not exist, add the following:

<Tool name=”Printing”>
  <caption>Print Current Map</caption>
  <category>Command</category>
  <image>print</image>
  <image_large>print_large</image_large>
  <style>image</style>
  <Assembly>Tadpole.GoSync.Mapbook.MapEngineUI.dll</Assembly>
  <TypeName>Tadpole.GoSync.Mapbook.MapEngineUI.PrintDisplay</TypeName>
</Tool>

This change must be applied to all of the appropriate configuration groups if more than one exists.  Save the changes and sync to client machines.

To do this, find SavedViews.xml in C:\GISDataServer\MobileDownloads\Default\MobileConfiguration (where C:\ is the root directory of your GO! Sync Mobile GIS Server, and Default is the client configuration group that the new view applies to).  Open and add a new <SavedView> either by copying an existing View, or using the code below with your information:

<SavedView name=”New MXD”>
  <!– Description is shown to the user in the open Saved View dialog –>
  <description>Specified View</description>
  <!– The name of the MXD that should be opened if the user select this Saved View –>
  <documentName>$data\MXD\New.mxd</documentName>
</SavedView>

Save these changes and sync from the client machine(s) to make the new MXD and Saved View available.

If your organization was using Franson GPS Gate on Windows XP client machines but now after upgrading to Windows 7 get an error when trying to use GPS in Mapbook, one customer has pointed out that in the Franson GPS Gate properties, by checking off “Run this program in compatibility mode for: Windows XP (Service Pack 3), and checking off “Run this program as an administrator” GPS will continue work in Mapbook as intended.  Checking off these options are shown below:

Both definition queries below distinguish inspections created on the same day or roughly a day, where the true value of “1” being used can be changed based on the number of days you want to go back.

pGDB – [INSPECTDATE] > Date() -1

fGDB – CURRENT_DATE – “InspectDate” <=1

Note: for fGDB’s definition queries will only work if referencing the alias field opposed to the true feature class name.  If you would like to see the above functionality for different MXD’s you will need to make the above change for each MXD.

Changing symbology to a pre-existing layer:

For your GO! Sync project if you are changing the symbology to a pre-existing layer, you will need to make the symbology change in ArcMap and then save your changes. The MXD’s being used by your project can be found in the $serverdata\MobileDownloads\Default\MXD folder location, where $serverdata is the server root directory and “Default” is the particular device group. If you have no device groups configured you will automatically be using the Default device group. The next time you run a sync from one of your client machine’s with GO! Sync installed you will see those changes you made.

How do I know which MXD to use?

If you only have 1 MXD you will be using the default MXD which can be found in this location: $ServerData\MobileDownloads\Default\MXD folder

I have multiple MXD’s for my project.  How do I know which one is my default?

If your GO! Sync project is configured to use multiple MXD’s and you want to identify the default MXD being used, navigate to the $serverdata\MobileDownloads\Default\MobileConfiguration and open the file called GoSyncMobileConfiguration.xml. Once open, search for the following tag:

<StartUpMXD></StartUpMXD>

Please note: If multiple MXD’s are being used, Mapbook automatically remembers the last MXD used in the application.

We created a new feature class – how can I add this to my GO! Sync project?

If your new layer was added to ArcSDE:

You will need to first navigate to your GO! Sync server and open the GO! Sync Extractor. This can be located by navigating to the Start menu and finding the GO! Sync folder.

Once open, click the Open Extract Configuration button

and navigate to your extractor configuration file (.xconf file) which is usually found in this location: $serverdata\ServerConfiguration\Extractor folder. If there is no .xconf file visible you can run a search in Windows explorer for $serverdata for “.xconf”.

What is the purpose of the .xconf file?

The .xconf file is used to store configuration information for extractor. This file, once opened with the extractor populates any existing destination or source geodatabases; its specific feature classes, auxiliary processes, and any additional output options applicable to destination geodatabases.

If your .xconf file(s) have already been created for you the best approach would be to utilize an existing .xconf file. Doing so avoids having to create a new .xconf file, and a corresponding scheduled task to run the extractor that uses the .xconf file.

Adding your new layer to the .xconf file:

In the extractor, if your new layer is visible but unchecked then this means you need to update your .xconf file by placing a check beside the layer and then saving your changes.

If this is a new layer then most likely there won’t be a check by the layer. If you cannot see your new layer among your other feature classes then your feature class does not exist in the source geodatabase specified.

*Please note that .xconf files can store multiple destination geodatabases and different corresponding source connection files in their respective drop down menus. It is recommended to verify you are using the proper connection information when location your new layer.

How do I change the symbology if my layer was added to a personal or file geodatabase?

If your new layer was added in a separate geodatabase:

1) Locate the Destination Geodatabase drop down in your .xconf file and add a new destination geodatabase. Ensure this geodatabase is different from the previous destination geodatabase.

2) Select the corresponding location of the Source Geodatabase for the new layer

3) Save the .xconf file 

Adding the layer to the .xconf file only has to be done once as these setting are saved in your .xconf file.  By adding the new layer in the .xconf file you are adding a layer to your other existing feature classes that are part of the FTP syncing process that occurs daily to each of your client machine’s. As long as the information is saved in the .xconf file the layer is permanently added to your GO! Sync project (permanent until you delete or remove).

Checking your project for your new layer:

To check for the new layer run a sync on the client machine and open Mapbook. If a client machine is not available, there is an option in the extractor to create an unzipped geodatabase which helps confirm if your feature class was added to your .xconf file successfully.

To get around this error:

• Turn UAC off:

• Restart your machine
• Regenerate license file with UAC still turned off using the “Create Client Details File” from the Start Menu\All Programs\GO! Sync location
• Send the .clf license file you just generated to support@tctechnology.com
• Navigate to the Start Menu\All Programs\GO! Sync location and choose “Load License Registration File” with UAC still turned off
• If your license loaded correctly you should see the screen below:

1.       Managing when data are available for sync

2.       Managing what type of data are available for sync

3.       Managing how data are packaged for sync

4.       Controlling GO! Sync program execution

5.       Limiting data updates to incremental changes

• A refined implementation of Esri Distributed Geodatabase framework

Managing when data are available is the simplest method for dealing with data synchronization challenges. In a typical implementation of GO! Sync, data are made available for download once per day – usually in the middle of the night. This prevents the majority of data downloads from occurring during peak load hours. GO! Sync only pulls data when changes are detected. Therefore, if the data published on the server do not change, then the client will not have anything to download and will only upload data throughout the day. Upload packages are very small (typically 2-5 KB) per package.

Managing what data are available is the most commonly used method to achieve significant performance improvements.  In addition to timing your updates, data updates can also be staggered.  Separate feature datasets can be packaged into separate geodatabases, and geodatabases can be post-processed to remove extraneous information.  For example, land base layers are updated less frequently than facility data therefore they are split into different geodatabases and distributed at different times. A typical approach is to update facility data nightly and land base data weekly.  This concept can be extended to segregate frequently updated features from rarely updated features as long as there are no geodatabase relationships that link the features.  Finally, GO! Sync customers commonly make use of standard or custom Auxiliary Processors to post-process geodatabases prior to distributing them.  A custom process could for example, strip out unneeded columns from the geodatabase and make the file much smaller by virtue of removing information that is unnecessary to support a particular business process.

All data are compacted and zipped prior to distribution.  When attempting to fully replace/update all of your data and total file size may be an issue, keep in mind that partial updates of individual sync sets are much smaller and again, data will only be downloaded when the server-side files change.

In addition to controlling when data are made available, GO! Sync can be further controlled at the client level.  The sync engine runs as a local service so a user need not be logged in to receive data updates. And when the user does log in, the program can be made to shut off and suspend all sync processing.

Limiting data updates to just the database deltas has the potential to substantially decrease the size of the update packages, but certainly increases the complexity of the system.  TCT’s approach to incremental updates is to maintain a replica on the GO! Sync Server and periodically difference that replica and register changes with GO! Sync.  The change packages are distributed and database state is managed at the client level.  If there is ever a state mismatch or other database failure, then the fail-over condition is to download the full replacement package.

In all cases, the synchronization actions are automatic and transparent to the end-user. They are never required to interact with the application to synchronize data updates.

Configuring Toggle Layer Functionality:

ToggleLayers.xml: location: <ServerDataRoot>\MobileDownloads\Default\MobileConfiguration\ToggleLayers.xml

1) Open the ToggleLayers.xml in the MobileConfiguration Folder.  *If you don’t have the ToggleLayers.xml file we can provide you this file or please contact your project manager to obtain this file and the ToggleLayers.xsd.

2) Update any LayerName Tag(s) to the layer(s) to be Toggled in GO! Sync Mapbook.

Here is what the code will look like:

<ToggleLayer>

<LayerName>LayerName1</LayerName>

<LayerName>LayerName2</LayerName>

<LayerName>LayerName3</LayerName>

<LayerName>LayerName4</LayerName>

<LayerName>LayerName5</LayerName>

</ToggleLayer>

</ToggleLayers>

3) Delete any LayerName tags that are not used.

4) Save and Close the xml document.

GoSyncMobileConfiguration.xml (GSMC.xml): location: <ServerDataRoot>\MobileDownloads\Default\MobileConfiguration\GoSyncMobileConfiguration.xml

5) Uncomment the Toggle Layer button in the GoSyncMobileConfiguration.xml file and save.  If you don’t have the code below you can copy and paste into your GoSyncMobileConfiguration.xml within the <Toolbar></Toolbar> section.

<Tool name=”CustomCommands_ToggleLayer”>
<caption>Toggle Layers</caption>
<category>Command</category>
<style>image</style>
<tag>CustomCommands_ToggleLayer</tag>
<image>ToggleLayers</image>
<image_large>ToggleLayers</image_large>
<Assembly>Tadpole.GoSync.Mapbook.MapEngineUI.dll</Assembly>
<TypeName>TCTechnology.GoSync.Mapbook.MapEngineUI.ToggleLayerTool</TypeName>
</Tool>

6) Open Mapbook

To get around this error:

• Uninstall GO! Sync Client.msi
• Completely turn off UAC
• Reboot machine and continue with the installation of GO! Sync Client.msi.

• Run the Mapbook desktop shortcut in elevated mode which can be done by right clicking and choosing to run as administrator

To edit the values, on the right hand side of the registry window right click the height value to a larger number, or if necessary also the width value and hit the OK button.  You will have to determine what size would be appropriate for your client machine as screen sizes vary.