Why Typing File Path in Windows Save As Dialog Seems Like Typing But Not When Using Simulate Click?

What’s Happening:

  1. Using Type Into to replace the default file name to a new name.
  2. The file path is typed correctly when seen with human eye.
  3. When I checked it, the file is saved in the default path with default file name.
  4. This only happend when using Type Into with Simulate Click ON or Set Text
  5. Tried this on 2 PCs with same computer specification

The problem solved when:

  • Using Type Into without Simulate Click

Environment:

  • Windows 7 Enterprise (Japanese version)
  • UiPath Studio Ver 2018.1.1

Question:
Any suggestion why this is happening?

Hi

I may have the same problem as you. i search an solution.

I dig up your post

I use the set text activity and I send the good path each time on a window “save as”. On a machine it works perfectly. On the other machine (same configuration) it saves the file to the target folder. It does not use the informed path. I do not understand why.

Hello @nico0702, nice to hear someone looking for a solution too. There are so many things I still don’t understand too, but by now when typing file path in Windows Save As dialog, I use regular way (no Simulate, no Send Windows Message) since it works each time with every device. It works fine though seems like a bit slow.

(In other time, the Simulate works on one PC and not on other PC too :D)

Sorry, I did not give how I solved the problem. I made sure to have the same file options on the machines. Since I no longer have the problem.
I activated the file extensions on the pc that was problematic, I activated the hidden files etc … Since that passes

1 Like

Hello @nico0702, thank you for sharing information!
If I remember well, the File Option was uniformed on the first stage of environment setting but it happened though. But a nice point to remember when building our automations later!

1 Like

@whyyouandi @nico0702

I am also facing the same issue.
Can anyone help…?

@Mohit_Sagar

I faced the issue too. The solution is to check “file extension” in view of the folder.

Thanks

1 Like