Configuring Vista Integration Parameters

The connection between Clue and Viewpoint Vista does not operate on a fixed, one-size-fits-all basis. Every organization has different equipment numbering conventions, company structures, and data ownership rules between systems. Configuring Vista Integration Parameters gives administrators precise control over how the integration behaves, what data syncs, which direction it flows, how equipment gets matched, and how edge cases are handled.

Over 45 configuration parameters are available, managed through the Clue admin panel under Global Parameters in the Integrations_vista group. Most parameters are set once during initial setup and remain unchanged. Others are adjusted as your fleet structure or Vista configuration evolves. Learn more about how the full Clue and Vista integration works at the platform level.

‍

Who Manages These?

• Clue Administrators and IT Teams manage integration parameters during initial setup and when organizational changes require adjustments to how data flows between systems.
• Your Clue Account Manager can also review and adjust parameters during setup or when your requirements change, particularly for complex multi-company configurations.

‍

Key Parameters Explained

Controlling What Syncs

Parameters in this group determine which data entities are included in the sync cycle. You can enable or disable syncing for equipment, projects, parts, employees, vendors, and other record types independently. This prevents unwanted data from flowing into Clue from Vista entities that are not relevant to your operation in Clue.

Equipment Matching and Filtering

viewpoint_use_sync_clue_field controls whether assets sync based on a custom UDF flag in Vista. When set to TRUE, only assets with the udSyncClueYN field marked as Y in Vista will sync to Clue. Assets marked N are excluded. This gives your team per-asset control over what appears in Clue without needing to modify the Vista equipment master structure.

Multi-Company Setup

vista_company_priority defines which Vista company codes (EMCo numbers) are included in the sync and in what priority order. Only companies listed in this parameter are synced. When Clue looks up equipment or employees for a work order, it searches each listed company in priority order until a match is found.

Work Order Defaults

Parameters in this group set default cost codes, job cost companies, and work order types that apply when records are created in Clue and pushed to Vista. These defaults ensure that work orders written in Clue land in the correct Vista cost structure without requiring manual code entry on every job.

Warranty Handling

When enabled, warranty parameters control how Vista's warranty data (from the EQMW table) syncs into Clue and which vendor records from the APVM table are linked to each warranty. These parameters determine sync frequency and how warranty records are matched to assets in Clue.

‍

Common Configuration Scenarios

• "We only want active equipment in Clue." Set viewpoint_use_sync_clue_field to TRUE. In Vista, mark each asset's udSyncClueYN field as Y or N. Only assets marked Y will sync. When a machine is sold or retired, set it to N in Vista and it stops appearing in Clue automatically.
• "We have multiple companies in Vista but only some should sync." Set vista_company_priority to include only the EMCo numbers you want, such as 1 and 3. Any company not listed is completely excluded from the sync. This is the correct approach for organizations where certain Vista entities are not relevant to Clue operations.
• "We do not want internal work orders going to Vista." Set vista_exclude_wo_export_by_type to the work order type codes for internal work such as INTERNAL or SHOP. Standard and PM work orders continue to sync normally while internal jobs stay within Clue only.
• "GPS hours are being overwritten by Vista during sync." Adjust vista_equipment_metadata_fields_from_duplicated to exclude hour-related fields from the Vista sync on linked records. Vista will continue updating fields like make, model, and department, but will leave engine hours and odometer for the GPS source to manage.

‍

Key Behaviors and Limitations

• Parameters are managed through the Clue admin panel. Standard users cannot access or modify integration parameters. Changes are made at the admin level only.
• Most parameters are set once during setup. The majority of configuration happens during initial integration setup and does not require ongoing adjustment. Parameters that control fleet filtering and company scope are the most likely to need updates as your organization changes.
• No code changes are required. All 45+ parameters are configurable through the admin panel. Adjusting how the integration behaves does not require development work or changes to your Vista installation.
• Testing mode is available. The vista_testing_mode parameter routes export data to a test payroll company (PRCo=99), keeping your production Vista data clean during setup and testing phases.

‍

Tips

• Review equipment matching parameters carefully during setup. If your Vista equipment IDs use different formatting than your GPS or telematics systems, configure the udCleanEquipNo UDF and matching parameters before the first sync to prevent duplicate asset records from being created.
• Add all relevant EMCo numbers to the company priority list before going live. Equipment in a company that is not listed will not sync. Missing a company during initial setup means that fleet data will be absent from Clue until the parameter is updated.
• Use testing mode before enabling live exports. Run the integration in testing mode first to confirm that work orders, timecards, and purchase orders are routing to the correct Vista cost codes and companies before allowing production data to sync.‍
• Document your parameter configuration. As your team grows and Clue administrators change, a written record of what each parameter is set to and why it was configured that way saves significant troubleshooting time when issues arise later.