Vista Visual Settings Guide

1. Connection Credentials

In Mosaic

Connection Credentials allow Mosaic to authenticate against your replicated Vista SQL Server database. Enter the fields below to establish the connection.

📝

In Vista: Vista data is mirrored to a SQL Server replica that your DBA provisions. A dedicated SQL Server login is created on that replica with read-only access to the replicated tables. See the SQL Server Integration Requirements for replication setup.

Fields

📘

The Server URL and Port are provisioned by your Mosaic Solutions team as part of the replication setup — they are not entered in this form. Port defaults to 1433.

To Get Started

1. Confirm SQL Server replication of your Vista database is set up per the SQL Server Integration Requirements.
2. Ensure your DBA has created a dedicated SQL Server login on the replicated database with read access to all Vista tables Mosaic relies on (see Vista Integrated Data for the full list).
3. Enter the credentials in the form and save.

After saving credentials, the agent will connect to the replica using the credentials above on port 1433 (or whatever port was provisioned with the server URL).

If the connection fails, double-check your credentials and confirm that the SQL Server login has been granted read access on the replicated database. Common issues include expired passwords, incorrect database names, or missing permissions on the replicated tables.

⚠️

Credentials may expire or rotate over time. Periodically return to this section to update your credentials so syncing is not interrupted.

1. Companies List

In Mosaic

The Companies List controls which Vista companies the integration reads from. Every fetch query is scoped to this list — projects, phases, time entries, employees, rates, and bill rates are only pulled when their JCCo, PRCo, or Co value is in the list.

📝

In Vista: Vista organizes data by Company (Co). Job Cost tables use JCCo, Payroll tables use PRCo, and shared tables (like budEmpRates) use Co. Most customers have one or two production companies, but multi-company customers can have many.

Setting Options

This is an array of integers. Enter the Vista Co IDs the integration should read from (e.g. [1], [1, 2], [10, 11, 20]).

• At least one company is required.
• Any company not in the list is excluded from sync — projects, phases, time entries, etc. for those companies will not appear in Mosaic.
• When the same project / phase / bill rate exists in multiple companies, Mosaic deduplicates and keeps the lowest-numbered company's copy.

📘

If you need to add or remove a company after go-live, coordinate with your CSM — re-sync may be needed for previously-excluded records to show up.

1. Project / Phase Fee Source

In Mosaic

The Fee Source determines where Mosaic pulls Project and Phase Fees from in Vista.

📝

In Vista: Vista does not have a single canonical "fee" field. Mosaic supports two sources:

• Contract Amount — sourced from bJCCM.ContractAmt. Available on Projects only — Phases do not have a contract amount in Vista.
• Total Cost — sourced from SUM(bJCCP.CurrEstCost) aggregated per phase. Available on Phases only — Project fee is then rolled up from phases by Mosaic.

Setting Options

• Contract Amount (default) — Project Fee = bJCCM.ContractAmt. Phase Fee is not set (it's rolled up in Mosaic from phase budgets, if any).
• Total Cost — Project Fee is not set from Vista (Mosaic aggregates it from phases). Phase Fee = SUM(bJCCP.CurrEstCost) per phase.

📘

This is a one-or-the-other choice — Project Fee and Phase Fee will never both have a source-set value. Pick the source that matches how your team thinks about fees: the lump contract value at the project level, or the bottoms-up phase rollup.

2. Project / Phase Budget Source

In Mosaic

The Budget Source determines where Mosaic pulls Project and Phase budget estimates from. Budget is used for spent-vs-budget reporting separately from Fee.

📝

In Vista: Same two sources as Fee:

• Contract Amount — bJCCM.ContractAmt, Projects only.
• Total Cost — SUM(bJCCP.CurrEstCost), Phases only.

Setting Options

• Contract Amount — Project Budget = bJCCM.ContractAmt. Phase Budget not set.
• Total Cost (default) — Project Budget not set. Phase Budget = SUM(bJCCP.CurrEstCost) per phase.

📘

Most customers use Contract Amount for Fees and Total Cost for Budgets — the contract amount represents what's been sold to the client (fee), and the cost-by-period rollup represents the internal budget. Confirm the right combination with your CSM before applying.

1. Time Entry Hourly Rate Source

In Mosaic

The Hourly Rate Source determines how Mosaic computes the hourly rate on each synced Time Entry.

📝

In Vista: There is no single "hourly rate" field on a Vista cost detail row. Mosaic supports two derivation methods:

• Actual Cost / Actual Hours — Computes the rate from the cost detail row directly: bJCCD.ActualCost / bJCCD.ActualHours.
• Custom Bill Rate Table — Looks up the most recent budEmpRates.BillableRate effective on or before the time entry's date for the employee. Requires the budEmpRates table.

Setting Options

• Actual Cost / Actual Hours (default) — Hourly rate = bJCCD.ActualCost / bJCCD.ActualHours. If your Vista instance does not have an ActualCost column, the calculated rate will be null.
• Custom Bill Rate Table — Hourly rate = the most recent budEmpRates.BillableRate effective on or before the entry's date. Requires the budEmpRates table to exist in your Vista instance. Time entries with no matching bill rate are skipped (logged as a warning).

⚠️

Switching to Custom Bill Rate Table without the budEmpRates table will cause time entries to drop from sync. Confirm the table is present before enabling.

📘

Both posted and unposted time entries are synced from Vista regardless of this setting — there is no filter on PostedDate.