26
Up to now, you can work in BC in the cloud with only very few existing code pages. You can count them on one hand:
MSDOS Use MS-DOS encoding format. It is the default value.
UTF8 Use UTF-8 encoding format.
UTF16 Use UTF-16 encoding format.
WINDOWS Use Windows encoding format.
For the connection of external systems, which however do not suffice the available code pages, there are currently big problems to bring the data correctly interpreted into the database. In the on premises version, the whole thing can be circumvented by working with DotNet and specifying the code page directly with a StreamReader, for example. In the cloud, you have no chance to pass this code page number directly, let alone set it. This can be very counterproductive, because there is no chance to work with slightly different encodings at all.
MSDOS Use MS-DOS encoding format. It is the default value.
UTF8 Use UTF-8 encoding format.
UTF16 Use UTF-16 encoding format.
WINDOWS Use Windows encoding format.
For the connection of external systems, which however do not suffice the available code pages, there are currently big problems to bring the data correctly interpreted into the database. In the on premises version, the whole thing can be circumvented by working with DotNet and specifying the code page directly with a StreamReader, for example. In the cloud, you have no chance to pass this code page number directly, let alone set it. This can be very counterproductive, because there is no chance to work with slightly different encodings at all.
STATUS DETAILS
Needs Votes
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team