
I'm looking at a number of customisation requests from a client looking to import MT940 statements to AX. They've asked me to populate the Trading party field on imported bank statements, but I believe this field may be denormalised in AX, unlike the Reference no or Entry reference fields that can be assigned directly through the BankStmtService.create service call that the whitepapers point to.
I've looked at the standard MT940XML_to_Reconciliation_xlst resource, and I can see the ReportEntryTradingParty tag calling the PartyId template. I can populate the CustVendNameSender tag with a custom MT940TXT_to_XML resource stylesheet, but even with the output from the second step transform, the screenshot above shows that the Trading party field isn't being populated on the bank statement.
Has anyone looked at populating this field through advanced bank reconciliation?
*This post is locked for comments
I have the same question (0)After digging further into \Classes\BankStmtService, I reached \Classes\AxBankStmtISOPartyIdentification and discovered that \Tables\BankStmtISOReportEntry was being populated with my desired Name value as the ID This led me to look again at the second transform on the MT940 port, and notice that whilst it's writing the PartyIdOrganisationGenericId tag in the AIF document, the call to the relevant template doesn't populate the OrgName parameter, so a simple change to the transform was enough to populate the table with the names I'm looking for. It's slightly disappointing to me that the relevant AIF services don't de-duplicate or normalise the data in any way (that is, providing identical party ID/name combinations twice in one statement will lead to two identical records in the AX table), but since I can't immediately identify anywhere else this table is used, I'm running with it.
Never sure about the etiquette of answering your own question, but hopefully this public contemplation helps someone...