The Generic XML Sync Settings page is available from the Synchronize Module located on the Main Admin page.

The Generic XML Sync Settings page lists the Main Dealer and each sub-dealer account (defined as an account with a dealer user assigned as the primary contact) as a separate row in the account grid.  This allows you to configure each with a different Generic XML server connection settings and/or push frequencies.  Placing a check in the appropriate Select row, performs a 2-way sync with all child accounts.  All sub-dealer accounts by default inherit the Generic XML server connection settings configured for the Main Dealer, unless otherwise specified.

Accompanied with the optional Public API, 3rd party application accounts  and devices are received and imported into Central.  Central accounts which already exist, will be mapped based on identical 3rd party application account names and by cross referencing the device serial numbers and equipment id's.  The remaining 3rd party application accounts which are not mapped are referred to as Account Orphans.  Using the Account Orphans page, accounts may be mapped to unlike names, or selected individually thereby creating new Central accounts.

Optionally, you can combine the Central Meter Validation results, allowing the meters extracted using Onsite, WebAudit or Viewer to be pre-approved by either the end-user or dealer employee prior to a PUSH; defined as the submission of data to the 3rd party application.  This process helps to reduce DSO (Day-Sales-Outstanding) by providing accurate and timely billing.

If FMAudit Central is offline and misses multiple syncs, then it only performs the last scheduled sync when it comes back online.

Generic XML Server Connection Settings
Minimally, the Main Dealer account requires the server connection settings to be specified.  To view another sub-dealer account and/or modify these settings, select the sub-dealer account from the Dealer Account drop-down list.  Modifying the Generic XML Server Connection Settings and selecting the Save Connection Settings button, applies those settings to the current sub-dealer account and all child accounts, no longer inheriting the settings from the Main Dealer.

Export Options
For flexibility, the Generic XML Sync allows you to output only managed or all device meters to one of three destinations, with the option to limit the file sizes.

XML Device Limit
To limit the data size transfer, i.e. email attachment, a device limit may be specified to subsequently break the data into multiple chunks.  The filename of the XML file is incremented appropriately.

Include Only Managed Devices
With this option selected, only managed device meters are pushed to the 3rd party application.  Managed Devices are automatically mapped via a Serial Number or Equipment ID during the receipt of information from the 3rd party application using the Public API, or may be manually mapped.

Export to File
The XML data file(s) are output to the default c:\Inetpub\wwwroot\FmaCentral\Temp path with the specified file name, incremented appropriately.

Submit to URL
This value is used to connect to the 3rd party application's web service.  If Central is hosted externally, this must include the external IP or domain path, i.e. http://3rdpartyapplication.dealerwebsite.com/APIService.asmx/.  If both Central and the 3rd party application are hosted internally, this may be the internal LAN IP or server name, i.e. http://172.1.120.3/APIService.asmx/, or http://servername/APIService.asmx/.

Send to Email
The XML data file(s) are attached to email(s) and sent to the specified address(es).

Meter Name Mapping
FMAudit products use static meter names, therefore the Generic XML Sync allows you to specify the associated 3rd party application meter names.  Fields are left blank for any meters which are not specified and used by the 3rd party application.

Map accounts by name
With this option checked, accounts submitted using the Public API that have like names to those in Central will be automatically mapped and selected for synchronization.  Accounts which are not mapped, are referred to as Account Orphans.  These accounts may be manually mapped via the Account Orphans page.  In the case where an audit is performed on an end-users WAN (Wide Area Network) therefore containing results from multiple branch offices, and the associated 3rd party application accounts are split, multiple 3rd party application accounts may be combined and mapped to a single Central account.  The account names are separated with a semi-colon ";".

Map accounts by EquipID's and S/N's
With this option selected, 3rd party application accounts submitted using the Public API; even with different names, are automatically mapped to the appropriate Central accounts.  Devices are auto-mapped based on a Serial Number or Equipment ID.  These devices may be manually mapped or edited via the ERP Equip ID column located on the Devices Management Views page.

Create accounts using Account Orphans
With this option selected, a Central account will be created automatically for each account orphan submitted using the Public API, based on the information extracted from the 3rd party application.  To individually select which 3rd party application accounts to create in Central, deselect this option and refer to the Account Orphans page.

Push Frequencies
Separate push frequencies may be configured as appropriate, i.e. Push meters from Central every 1 day.  These settings apply to all child accounts.  Each push will submit the updated meters since the last interval, i.e. previous day.  To define the meter submission frequency on a per-account basis, refer to the Account Settings page.

Send results via email
With this option checked, a summary email will be sent to the selected contact upon completion of a push to the 3rd party application.