Power Automate Desktop Latest Version Issue

[Anonymous]

Hi Microsoft,

I just upgraded my PAD to the latest version. After upgraded, I noticed I can't copy the codes from my txt file and paste into PAD. Fyi, I have no such issue with the older version.

Appreciate if you could advise how to overcome the above issue.

[kinuasa]

Hi,
The following code must be added to the end of the previous flow.

Regards,
kinuasa

# [ControlRepository][PowerAutomateDesktop]

{
  "ControlRepositorySymbols": [],
  "ImageRepositorySymbol": {
    "Name": "imgrepo",
    "ImportMetadata": {},
    "Repository": "{\r\n  \"Folders\": [],\r\n  \"Images\": [],\r\n  \"Version\": 1\r\n}"
  }
}

[Anonymous]

Hi @kinuasa ,

Thank you so much for the response. The solution provided is not working. Let me brief you the scenario.

When I created a project, I will press "Ctrl + A" to select all visuals and "Ctrl + C" to copy all visuals and "Ctrl + V" to paste into my notepad. After I installed a new version of PAD, I opened a new flow in PAD and copy all my previous codes from notepad and paste (Ctrl + V) into the blank page in PAD, all the visuals will appear automatically. This methods works perfectly fine in the previous PAD version. Unfortunately, after upgraded to the latest PAD version, I can't paste the code to PAD anymore. Any advise?

[kinuasa]

Below is a sample.

The following is code that had no problem until version 2.17, but cannot be pasted in version 2.18.

Scripting.RunPowershellScript Script: $'''#Power Automate for desktopのバージョンを取得
#※ストアアプリ版とインストーラー版の両方がインストールされている場合については考慮していません。
$padConsoleProcess = Get-Process -Name \"PAD.Console.Host\" -ErrorAction SilentlyContinue
if($padConsoleProcess){
  $padConsolePath = $padConsoleProcess.Path
  if($padConsolePath -like \"*WindowsApps*\"){
    #ストアアプリ版
    #「PAD.Console.Host.exe」のプロパティからバージョン情報を取得
    $padVersion = (Get-ItemProperty $padConsolePath).VersionInfo.ProductVersion
  }else{
    #インストーラー版
    #レジストリのUninstallキー以下からバージョン情報を取得
    $padVersion = (Get-ChildItem -Path (\"HKLM:SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\", \"HKLM:SOFTWARE\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall\") | ForEach-Object {Get-ItemProperty $_.PsPath} | Where-Object {($_.DisplayName -eq \"Power Automate for desktop\") -and ($_.BundleVersion -ne $NULL)}).BundleVersion
  }
  Write-Output $padVersion
}''' ScriptOutput=> PowershellOutput ScriptError=> ScriptError
SET PadVersion TO PowershellOutput.Trimmed

The following is a code that can be pasted without any problem in version 2.18.

Scripting.RunPowershellScript Script: $'''#Power Automate for desktopのバージョンを取得
#※ストアアプリ版とインストーラー版の両方がインストールされている場合については考慮していません。
$padConsoleProcess = Get-Process -Name \"PAD.Console.Host\" -ErrorAction SilentlyContinue
if($padConsoleProcess){
  $padConsolePath = $padConsoleProcess.Path
  if($padConsolePath -like \"*WindowsApps*\"){
    #ストアアプリ版
    #「PAD.Console.Host.exe」のプロパティからバージョン情報を取得
    $padVersion = (Get-ItemProperty $padConsolePath).VersionInfo.ProductVersion
  }else{
    #インストーラー版
    #レジストリのUninstallキー以下からバージョン情報を取得
    $padVersion = (Get-ChildItem -Path (\"HKLM:SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\", \"HKLM:SOFTWARE\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall\") | ForEach-Object {Get-ItemProperty $_.PsPath} | Where-Object {($_.DisplayName -eq \"Power Automate for desktop\") -and ($_.BundleVersion -ne $NULL)}).BundleVersion
  }
  Write-Output $padVersion
}''' ScriptOutput=> PowershellOutput ScriptError=> ScriptError
SET PadVersion TO PowershellOutput.Trimmed

# [ControlRepository][PowerAutomateDesktop]

{
  "ControlRepositorySymbols": [],
  "ImageRepositorySymbol": {
    "Name": "imgrepo",
    "ImportMetadata": {},
    "Repository": "{\r\n  \"Folders\": [],\r\n  \"Images\": [],\r\n  \"Version\": 1\r\n}"
  }
}

[Anonymous]

Hi @kinuasa,

I have tested your code, it works. But, I can't use your code because my original code got ControlRepositorySymbols and ImageRepositorySymbol. I need to import all my original symbols to PAD, otherwise it is very painful to recreate everything.

[Anonymous]

Hi, @Anonymous when you are copying  and pasting the code

,both pad version must be same. then only it will work.

[Anonymous]

Hi @Anonymous ,

All the while when I upgraded my PAD, I have no issue to copy and paste the code from old PAD to new PAD. Only this time, I can't paste into New PAD. Not sure happened to the latest PAD version.

Do you know where can I get back the old PAD version? Otherwise, I need to create all symbols one by one. It is really a painful process.

[Anonymous]

There is no option to get back to old version @Anonymous , one option is there, if you have old code in pad update the pad copy the code and paste the code in new version pad.

[Anonymous]

Thanks @Anonymous. This solution not working for me because the PAD auto update not working for my machine. So if got any PAD update, I need to uninstall the old PAD first and then only can install the new PAD in my machine.

[Anonymous]

Hi @Anonymous ,

I tried to re-create all the symbols. But, I got the below error messages. The latest PAD version seems not really stable.

Message = Exception has been thrown by the target of an invocation.
Error = System.Reflection.TargetInvocationException
Full text = System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: Sequence contains no matching element
   at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source, Func`2 predicate)
   at Microsoft.Flow.RPA.Desktop.Designer.UI.ProgramItemConfiguration.Pickers.ControlPicker.ViewModels.ControlPickerViewModel.OnScreenAdded(ScreenAddedEvent e)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at Microsoft.Flow.RPA.Desktop.Shared.ApplicationFlow.Internal.ApplicationEvents.RaiseInternal[T](T domainEvent)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Correlation ID: 0b870ca1-7c1f-4772-9aec-5ce719efd1df

[Anonymous]

Hi @Ahammad_Riyaz  @VJR, & u guys have any solution for this issue?

[Pavel_NaNoi]

Take your actions, put em in a .txt file and put the following:

Put this after all actions but just before the huge slab of encrypted text:

# [ControlRepository][PowerAutomateDesktop]

{
"ControlRepositorySymbols": [
{
"Name": "appmask",
"ImportMetadata": {
"DisplayName": "Computer",
"ConnectionString": "",
"Type": "Local"
},
"Repository": "{\r\n \"Screens\": [\r\n {\r\n \"Controls\": [\r\n {\r\n \"AutomationProtocol\": \"uia3\",\r\n \"ScreenShot\": \

and then after that huge slab of text put this in:

"ImageRepositorySymbol": {
"Name": "imgrepo",
"ImportMetadata": {},
"Repository": "{\r\n \"Folders\": [],\r\n \"Images\": [],\r\n \"Version\": 1\r\n}"
}
}

see if that works.

[Anonymous]

Hi @Pavel_NaNoi,

Thanks for you support. The above codes not workable for me because my previous codes got ControlRepositorySymbols and ImageRepositorySymbol which I need to bring to the new PAD version.

Aside to @Anonymous,

Now I can assign all symbols without any problems, the error message no longer prompted.

Thank you so much for all your support, I really appreciate that. You may close the case.

[AndersonFoBr]

NEVER use Notepad for that. Use Notepad++ or other better text editors.
Most Notepad versions out there have severe memory limitations that results in data loss with pasting PAD code to it.

[Agnius]

The thing with updates is that some PAD updates also come with an update to Robin core. Robin is the proprietary language that you can see when you copy your actions from PAD to a text editor. And when Robin core gets updated, the syntax of some actions changes. When this is the case, this can either prevent the entire code from being pasted into PAD, or (in later versions) the affected action will be created as "Unknown action" while those that are unaffected will be pasted properly.

So, using the flows stored in text files as a way to transfer code from one version of PAD to another is a bad idea, usually. We do store our code in text files for code review and version control reasons, but we usually keep it up to date with PAD updates. It cannot be trusted to work with a different version of PAD than the one it was saved in.

-------------------------------------------------------------------------
If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.

I also provide paid consultancy and development services using Power Automate. If you're interested, DM me and we can discuss it.