MessageBox no longer work well with variables

Feedback StudioX
,
1

I have an automation with several MessageBox activities (UiPath.Core.Activities.MessageBox ) with variables (strings) in the input text, and it worked well for a long while, but recently after on of the updates, when running, it’s no longer displaying the Message Box, completely as if the activity was comment out.

3

@Udiar,

Please share more details like StudioX version and other details which will be helpful to recreate the scenario.

For now, check if your Antivirus software is blocking the message box. Try once by disabling the anti virus software if it works.

4

Thanks for your reply.
When no variables, the MessageBox works fine, so I guess it’s not the Antivirus (otherwise Antivirus would also block the MessageBox without variables).

StudioX Community Edition 2024.10.4
Packages are in the following screenshot.

The image shows the "Manage Packages" window in UiPath Studio, specifically the "Project Dependencies" section, listing various activity packages along with their versions and notes on compatibility. (Captioned by AI)
The image shows the "Manage Packages" window in UiPath Studio, specifically the "Project Dependencies" section, listing various activity packages along with their versions and notes on compatibility. (Captioned by AI)1661×960 129 KB

5

Could you please share the workflow screenshot as well

6

Here it is:

The image shows a UiPath Expression Editor window with a message box configuration summarizing specific data fields and respective values to be reviewed, including activity, current iteration, case type, email, and various identifiers. (Captioned by AI)
The image shows a UiPath Expression Editor window with a message box configuration summarizing specific data fields and respective values to be reviewed, including activity, current iteration, case type, email, and various identifiers. (Captioned by AI)1248×1428 139 KB

7

Try storing the value into a variable and see the value coming in Locals. If it is coming as expected - Use a substring function to limit the characters and see if the message box is coming as expected. If it works fine - give the full variable without limitation. If it fails for full characters- Use substring and Increase the character limit and see where it is breaking

responseString.Substring(0, 100)

8

@Udiar,

Can you try preparing this string in a variable and then pass only that variable to the message box?

9

Thank you for the excellent advice Sharaz !
I tried it and found out that the breaking point is a double-quote char [ " <=> Chr(34) ] which was part of a string variable (one of the compounding variables of the message).
The question is: Whereas the double-quote char was always there and it was displayed well until recently, why the latest updates caused it to be unsupported ?!

2 Likes
10

Glad that it helped you
While opening in the latest upgrade - it could have added due to some technical glitch. Not sure

12

Hi @Udiar

Was your update maybe also related to an upgrade from a Legacy type process to a Windows type process?

13

No, it was on only packages updates, and possibly version updates.

14

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.

16

If you still have a way to test this - does it work with the System 24.10.7?