Write CSV with encoding fail

[Romain_80000 (Romain)]

Hi Everyone,

I’m trying to write a csv file with WriteCsvFile Activity using encoding “iso-8859-15”.
But I’ve an error on execution.

“Ecrire fichier CSV: ‘iso-8859-15’ is not a supported encoding name. For information on defining a custom encoding, see the documentation for the Encoding.RegisterProvider method. (Parameter ‘name’)”

I’ve tried “iso-8859-1”, “ASCII-us” but I have the same error.
I’m using Studio 2023.4.2

Regards

[Palaniyappan (Palaniyappan P)]

Hi

The error you’re encountering is because the “iso-8859-15” encoding is not supported directly in UiPath’s Write CSV activity.
U can check this doc
https://docs.uipath.com/activities/other/latest/workflow/supported-character-encoding

Hope this clarifies

Cheers @Romain_80000

[Praveen_Mudhiraj]

The error message indicates that “iso-8859-15” is not a supported encoding name. This is because the .NET Framework used by UiPath may not include this specific encoding by default.

you can try the following steps… Hope may help

1.Use a Supported Encoding: Instead of “iso-8859-15,” try using a supported encoding like “ISO-8859-1” (also known as Latin-1) which is more commonly available

2.Use “Windows-1252” Encoding: If ISO-8859-1 doesn’t work, you can try using “Windows-1252” encoding, which is similar to ISO-8859-1.

3.Custom Encoding: If you absolutely need to use “iso-8859-15” and it’s not available by default, you may need to create a custom encoding provider using Encoding.RegisterProvider as suggested in the error message. However, this is a more advanced step and may require coding expertise.

Here’s an example of how you might use “ISO-8859-1” encoding in UiPath:

Encoding.GetEncoding(“ISO-8859-1”).GetString(yourBytes)

@Romain_80000

[ppr (Peter Preuss)]

@Romain_80000

For information on defining a custom encoding, see the documentation for the Encoding.RegisterProvider method. (Parameter ‘name’)

Tracker:

[InfoSet] - LegacyToWindows Migration # Issue - Mapping Set - Fix Tracker

This post is currently in a preview version. New statuses are checked regularly and trackers are updated Introduction In the past, problems have been observed within legacy-to-Windows code conversions. Workarounds have been found for some of these problems. From this, a mapping set could be derived. At a later time fixes were realized and the problems were remedied. In this part of the [InfoSet] - LegacyToWindows Migration series, the issue, and the related progress are tracked. Scope With…

Workaround, when an UiPath.System.Activities / UiPath.Excel.Activities Package Version is used, which has not already adapted:
2.11 Unsupported specific character encoding

[Yoichi]

Hi,

Can you try to call System.Text.Encoding.RegisterProvider(System.Text.CodePagesEncodingProvider.Instance) using InvokeMethod as the following sample?

Sample20230926-1.zip (3.0 KB)

Regards,

[Romain_80000 (Romain)]

Thank you all for your help.

@Praveen_Mudhiraj
Do you have an example of using Encoding.RegisterProvider in C#.

@Yoichi
Thanks but I have a compilation error. I’m in C# maybe that’s the cause. Do you have the same thing in C#?

[Yoichi]

HI,

How about the following?

Sample
Sample20230925-1CS.zip (3.2 KB)

Regards,

[Romain_80000 (Romain)]

@Yoichi

Thank you very much, I understand, if we copy and paste the method it does not put the references in the workflow.
Typing by hand solved the problem.

どうもありがとう