Updates & Issues

When syncing Salesforce data via the Bulk API CSV format, multi-line field values (such as `BillingStreet` on Accounts) that contain CRLF or lone CR line breaks have those line breaks silently changed to LF, so a value returned by Salesforce as `line1\r\nline2` ends up stored as `line1\nline2`.

After an administrator refreshes or restores a Dataverse environment, the sync service can continue reporting every run as successful while it actually copies no data at all, including brand-new changes made after the restore. This can persist for a long time with no error or warning shown to anyone, so the destination silently falls out of date.

This is a planned enhancement — not yet available — that would let an admin temporarily switch a sync profile from hourly to a 5-minute cadence for up to 8 hours so test changes show up faster.

We're designing a way for admins to specify that a table should wait until a related "parent" table finishes syncing, to close the brief window where a report can show a child record (e.g. a Transaction) before its related parent record (e.g. a Contact) has synced.

Three Dataverse-specific settings that control how long lookup labels, choice labels, and multi-select values can be before truncation are currently set on the profile-level configuration instead of on the individual Dataverse source, so they show up (and can be edited) even for non-Dataverse sources where they have no effect.

On the All Runs page, viewing extra columns or paging through run history requires scrolling down the whole page first, because the horizontal scrollbar and pagination controls are pushed below the visible screen area.

On the All Runs page, a run that already failed can show its State column as `Failed` while the Error State column still shows a blue, spinning `Loading` indicator, making a failed run look like it's still in progress.

The target schema/mapping view for Dataverse-based connections shows each column's SQL destination details (SQL column, type, nullable, primary key) but does not show the original Dataverse attribute type (e.g. Lookup, Picklist, DateTime, Money), so customers can't see the full source-to-target column mapping in one place.

Syncing Dataverse tables with lookup fields produces two columns holding the same display text — for example both `<lookup_field>name` and `<lookup_field>_label` contain the same value.

When creating a profile through the onboarding or "Add profile" wizard, advanced replication settings such as target table prefix, Dataverse synthetic-column lengths, and source page sizes are not exposed, so they can only be configured after the profile already exists.

This adds a one-click option to show every available column in the activity-history view at once, and makes the change-details popup larger so that long lists of changes are easier to read.

When a data refresh is cancelled, it can sometimes remain shown as still in the middle of cancelling and never move on to a finished state. This leaves the activity history looking misleading, even though later refreshes of the same data complete normally.

Synced tables on Azure SQL targets always use the raw entity name (e.g. `<entity>` and `stage_<entity>`), with no way to add a custom prefix to namespace them.

When selecting tables to sync (Dataverse, Dynamics BC Online, or Salesforce), the picker only shows the friendly display name, so searching by the underlying schema/logical name (e.g. `incident`) returns no results even though the table is listed as `Case`.

Customers who need to allow-list the fixed outbound IP address used by sync/ETL traffic on their firewall currently have no way to find that IP address in the profile page or account settings and must contact support to obtain it.

Syncing a Salesforce Data Cloud DLM object (such as an Account DLM entity) fails and eventually disables the source table because the sync tries to query a `LastModifiedDate` column that doesn't exist on that object, producing an error like `INVALID_FIELD: No such column 'LastModifiedDate' on entity '<Data Cloud DLM object>'`.