Im currently working on the HSBC BAC Export for a customer in NAV 2018, which has had all the BAC's functionality removed by MS.
The BACS file is a standard 18 file format as shown below :
VOL1000024 801014 1
HDR1A801014S 180101400002400010000 10243 102450000000
HDR2F0102400100 00
UHL1 10244999999 000000001 DAILY 000
0901277777777701709012774859633000000000001000A.N.Y.COMPANY GENERICREF1 MR R BLOGS
0901273333333301709012774859633000000000001000A.N.Y.COMPANY GENERICREF2 MRS A PERSON
0901274444444401709012774859633000000000001000A.N.Y.COMPANY GENERICREF3 MR G SMITH
0901279999999901709012774859633000000000001000A.N.Y.COMPANY GENERICREF4 MISS J DOE
0901277485555501709012774859633000000000001000A.N.Y.COMPANY ED101452 MR ED
0901277485963309909012774859633000000000005000TEST PAY CONTRA A.N.Y.COMPANY
EOF1A801014S 180101400002400010000 10243 102450000000
EOF2F0102400100 00
UTL10000000005000000000000500000000050000001 0000000TEST PAY
Up until now we have not been able to get an answer from Microsoft as to how we can use header and footer lines with Data Exchange Definitions, so it looks like we might have to go down the route of re-inventing the while and putting the BACS files back into NAV 2018 in the custom object ranges.
Has anyone managed to get this working yet, as Im sure we are not the first to need to do a HSBC export.
0
Answers
I have got the same problem in BC23, I can't believe no one reported/resolved it?!