When you synchronize vendor data between companies in Business Central, you can run into a conflict where the vendor cannot be created before its bank account exists, and the bank account cannot be created before the vendor. The fix is to remove the field validation on the preferred bank account code in the data template, so the vendor synchronizes first and the bank account follows right after.
You make this change by setting the relevant data template to development, locating the preferred bank account code field, unchecking the Validate field, and setting the template back to released.
This is safe because the validation has already been performed in the master company, so the value is correct even though it is not validated again during synchronization.
Why vendor and bank account synchronization can fail
When you set up synchronization between companies, you sometimes need to remove the field validation on the data template line so the synchronization can run. A typical example is vendors and vendor bank accounts, where the two records depend on each other.
On a vendor, the preferred bank account code may be filled out. When that field is populated, it can also be synchronized when you synchronize the vendor. The problem appears the moment you synchronize a new vendor: the bank account has not yet been created in the subscriber company.
That creates a conflict. The vendor cannot be created before the bank account is created, but the bank account cannot be created before the vendor. The synchronization is stuck in a circular dependency.
How removing field validation solves the conflict
Because the validation has already been done in the master company, you can safely remove the validation of the bank account code on the subscriber side. The value is correct, so you do not need to validate it again during synchronization.
With the validation removed, the synchronization runs smoothly. The vendor is created first with the preferred bank account code forced in as a value, and the bank account itself is synchronized right after.
How to remove the field validation in the data template
Open the data template for the vendor and set it under development. Find the field for the preferred bank account code. Mark the Validate field and uncheck it, then set the data template back to released.
From that point, the preferred bank account code is no longer validated during synchronization. The value is forced in, and the bank account code is created immediately afterwards.
Q&A
Why can’t a vendor and its bank account be synchronized at the same time?
The two records depend on each other. The vendor cannot be created before the bank account exists, and the bank account cannot be created before the vendor. This circular dependency causes a synchronization conflict for new vendors where the preferred bank account code is filled out.
How do I remove field validation on a data template in Business Central?
Open the data template, set it under development, find the relevant field such as the preferred bank account code, mark the Validate field and uncheck it, then set the data template back to released.
Is it safe to remove the validation on the bank account code?
Yes. The validation has already been performed in the master company, so the value is correct. Removing the validation on the subscriber side only skips a repeated check, and the bank account code is created right after the vendor synchronizes.