Troubleshooting
In XrmToolBox
The tool does not appear in the Tool Library
Replisteer needs XrmToolBox 1.2023.10.67 or later. Update XrmToolBox (Help > Check for updates, or download the latest version).
Column names are red, or ‘Column … does not exist’
The name is not in the loaded target columns. Click Load columns (Targets tab) or Load fields (Steps tab), and check the spelling: Dataverse columns use logical names (emailaddress1, not Email).
A formula uses a field that ‘will be empty’
The name is not a source field or variable. Load the source fields (Source tab, Load fields) and check the spelling. Names with spaces or special characters need brackets: [First Name]. Linked-table columns of FetchXML keep their alias: acc.accountnumber.
‘… expects a number, got 12,50’
The value uses a decimal comma. Convert it: NUMBER(price, ","). Numbers in text use . as decimal separator; Replisteer never guesses because 1,500 could be one and a half or fifteen hundred.
A lookup column fails: ‘can reference account, contact; use CreateEntityReference’
The column can point to several tables (customer, owner, regarding), so a bare GUID is not enough. Say which table: CreateEntityReference("account", id).
An update or upsert changes nothing
No record matches all match criteria. Preview the step and compare the criteria values with the target data: text must match exactly (the comparison in Dataverse follows its own rules for case), and "007" is not "7". Trim and normalise values in the criteria, for example LOWERCASE(TRIM(email)).
An upsert creates duplicates
Upserts match on the criteria you give. Make sure they identify one record (a business key), and that the inserted record gets the same values the criteria look for: map the key column too.
Plug-ins slow a migration down, or fail it
On the target’s Options…, check Bypass custom plug-ins and workflows (requires the prvBypassCustomPlugins privilege) and Do not send unchanged values, which avoids updates that change nothing.
Passwords are missing after opening a project
The project was saved by another Windows account, on another computer, or without passwords. Enter them again in the SQL Server connection dialog. See Passwords and secrets.
Command line
Windows protected your PC
The runner is not code-signed yet. Choose More info > Run anyway, or unblock the downloaded zip before extracting it (right-click > Properties > Unblock).
’needs a connection string'
Outside XrmToolBox every Dataverse connection needs a connection string, and SQL Server connections need one when their password is not readable. The message says the exact option and environment variable to use. See Connection strings.
Connecting to Dataverse fails
Check the Url (the environment address, https://<org>.crm<n>.dynamics.com), the application id and the secret (secrets expire). The app registration must be an application user of the environment with a security role. replisteer validate tests the connection without writing anything.
SQL Server: ‘The certificate chain was issued by an authority that is not trusted’
The server uses a certificate the computer does not trust (common for on-premises and development servers). Add TrustServerCertificate=true to the connection string, or install the server’s certificate.
The scheduled task shows 0x3
The project or its connections are not valid and nothing ran. Run the task’s command in a Command Prompt to see the message, or open the log file.
Still stuck?
Open an issue on GitHub. Run with --output result.json (or export the log in XrmToolBox) and include the messages. Remove connection details first: Replisteer never writes secrets to its output, but your data may be in the source values of failed rows.