Add Queue Item and Get Reference - Local characters ÅÄÖ break

[tuokyh]

Hello,

When adding queue items by using the persistence pack activity “Add Queue Item and Get Reference”, any local characters (ÅÄÖ) in Specific Data values break. For example, “ä” changes to “\u00e4”.

The problem is easy to replicate, just add any queue item using the mentioned activity, with some special local characters, and they should break.

Just in case, please find attached a very simple project showing the difference in behaviour between the traditional “Add Queue Item” and this new persistence version of the same activity. You will have to create a queue to Orchestrator for the project to work, obviously.

OrchestrationProcessFail.zip (7.4 KB)

[loginerror (Maciej Kuźmicz)]

Hi @tuokyh

It is a known issue and our team is aware of it. Please go over this topic, it should contains the clues to overcome the issue with some workarounds:

Bulk Add Queue Items write nonenglish values

I’m writing a robot in which speed matters and found activity Bulk Add Queue Items quite useful because adding around 100 items by Add Queue Item activity takes tens of seconds which is quite long for process. I noticed that Bulk Add Queue Items adds nonenglish text as unicode entities, though Add Queue Item activity works as expected. It’s not a problem to convert from unicode entities to readable text but it looks quite off and also human can’t understand these queue items. It would be great…

[OnurSen]

I have also the same issue and I found some Solutions from UiPath Forum about this Problem , but the Solutions doesnt work for me

I tried the following solution idea but it didn’t work.

[Solved] The trouble with the queues and non-ASCII characters

With the v2018.4 orchestrator, non-ascii characters that are posted as string members of a QueueItem are escaped: [image] Among the people who are facing the same issue, has anyone come up with a “nice” alternative solution for embedding special characters into a QueueItem, while keeping them readable (i.e. not by converting the text to base64)?

[loginerror (Maciej Kuźmicz)]

Hi @tuokyh

The original issue seems to be fixed. I’ve just tried your sample project on the latest version of Studio 20.10.1, with your old versions of packages:

And it seems to have worked as you would expect: