4

Data Exchange Definition - Ability to insert Carriage Return as a Custom Column Separator


Data Exchange Definition is a great tool to be used in order to generate files with the required formats to be imported as Bank Payments.

 

Recently, we received a requirement to have one line per field instead of one column per field.

The first 25 lines represents the first payment record, after line 26 until 50 represents the second payment and so on.

 

To achieve this without customisation, it's required to be possible to select 'CR/LF' in Custom Column Separator field and being interpreted as Carriage Return/Line Feed. At the minute, if we type 'CR/LF' in Custom Column Separator, the file is generated with 'CR/LF' between columns instead of transforming it as Carriage Return/Line Feed.

 

As a workaround, we cloned the xmlport 1230 "Export Generic CSV" and we added the line of code FieldSeparator = 'LessSymbolCR/LFPlusSymbol'.

 

It would be great to have this option in core standard product.


IMPORTANT NOTE: When you read 'CR/LF' you should read 'LessSymbolCR/LFPlusSymbol'

By LessSymbol and PlusSymbol we mean the math symbols.


By unknown reason, these symbols are not allowed in this form. We received the message: "We have encounter some malicious input. Please remove that and try again"

https://community.dynamics.com/business/f/dynamics-365-business-central-forum/487552/data-exchange-definition-to-export-a-bank-payment-file---one-line-per-field

STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for your feedback. Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.


Sincerely,
Aleksandar Totovic
PM, Microsoft