“Record(272) is not compatible with Codeunit.Run(Record(1220))”
If you are trying to run the Positive Pay Export in Microsoft Dynamics 365 Business Central for the first time and you are getting this error, you have probably been using Business Central for a year or more.
What is more frustrating than getting an error you can’t find an answer to when you search? It is that you can recreate the error in your sandbox, but not in the Preview Sandbox. If this is a bug with a recent fix, you think you would find all sorts of posts about it when you search, but you don’t. Export Positive Pay Files – Business Central | Microsoft Learn doesn’t tell you what to do when it doesn’t work.
The error “Record(272) is not compatible with Codeunit.Run(Record(1220))” refers to the Check Ledger Entry and Data Exchange Definition tables. And you find that you get the same error no matter what positive pay export Data Exchange Definition you select to run from the Bank Export/Import Setup record you have assigned to the bank account card.
You get the same error even when you use the Bank of America or Citibank examples provided in the setup data from when your company was created. It’s not just your new Data Exchange Definition to meet your bank requirements that’s the problem.
But wait! Maybe that’s the key? The only thing in common is the Bank Export/Import Setup. Is there something not right about the setup data that was provided back when the company was originally created? Cronus Company demo data in the Preview Sandbox will have newer setup and sample data.
Compare the data between older companies created using setup data and what is currently in Preview Sandbox, and you will find your answer. The Bank Export/Import Setup does not include the correct Processing Codeunit ID in older setup data from the US localization. The old setup data uses Processing Codeunit ID 1709 Exp. External Data Pos. Pay for Export-Positive Pay.
The Processing Codeunit needed to eliminate the error is 1700 Exp. Launcher Pos. Pay. The problem was obviously fixed in code somewhere along the line because, if you add a new record today to the Bank Export/Import Setup list and select Export-Positive Pay as your Direction, 1700 Exp. Launcher Pos. Pay defaults into Processing Codeunit ID.
The answer is…… select 1700 Exp. Launcher Pos. Pay for the Processing Codeunit ID for all Export-Positive Pay records in the Bank Export/Import Setup list when setting up Positive Pay in Business Central in the United States.
