Transaction Broker connectivity failures
The Transaction Broker imports data into FactoryMaster via CSV files. Connectivity failures usually mean the broker cannot locate, read, or process the file.
The broker is not picking up files automatically
If a broker is not running, FactoryMaster will display a system status message on the homepage. See Error - 'A broker is logged out' system status message for steps to resolve this.
Check the folder path the broker is monitoring. If the path has changed, for example, after a server migration or a Windows update — update it in the broker configuration.
Confirm the file being dropped into the folder matches the expected format: CSV, with Column A containing the correct Transaction Type code for the record being imported.
Check that the service account running the broker has read and write access to the monitored folder.
If the broker is set to run on a schedule and the schedule has been disrupted, see Setting up Scheduled Programs to reconfigure it.
The broker is running, but transactions are failing
Go to General, click Transaction Broker, then click Transaction Broker Import Menu. Review the results screen — failed rows are highlighted in red, with the error reason shown at the bottom of the screen.
Check for these common failure reasons:
Incorrect Transaction Type code in Column A.
Missing compulsory fields (shown in bold in the Transaction Structure).
A referenced record — such as a Supplier or Part Number — that does not exist in FactoryMaster.
To correct a failed record without re-importing the whole file, switch to Modify Mode, overtype the incorrect field directly in the results screen, then click Resubmit Transaction.
If the same error is recurring across many records, go to General, click Transaction Broker, then click View Transaction Structures. Open the structure for the relevant record type and compare it against your CSV layout.
📌 Note: Column A must always contain the exact Transaction Type code as shown in the Transaction Structure. A mismatch — including extra spaces — will cause the record to fail.
Field mapping errors
Field mapping issues occur when CSV data cannot be correctly matched to a FactoryMaster record type or field.
Go to General, click Transaction Broker, then click View Transaction Structures. Open the structure for the relevant record type.
Compare the field order in your CSV against the structure. The columns must be in exactly the correct order, and Column A must always be the Transaction Type code.
Check for any compulsory fields shown in bold in the structure. If a compulsory field is blank or in the wrong column, the record will fail.
Correct your CSV layout and re-import. If a previously processed record failed and needs to be resubmitted, switch to Modify Mode in the results screen, then click Resubmit Transaction.
Still need help?
If the issue persists after working through the relevant section above, raise a support case online. Include the error message or behaviour you are seeing and the date the issue started — this allows the team to investigate without needing to ask for additional information.