web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / There is a bug in the ...
Power Automate
Suggested Answer

There is a bug in the split Excel worksheet operation.

(1) ShareShare
ReportReport
Posted on by 331
After trying different methods many times, I found that when the Excel worksheet is split, the PAD process is invalid for the VBA button(copy_fx). It has no errors but skips the button (process 80). I need to cancel the window split to press the button normally?
 
I have the same question (0)
  • Suggested answer
    trice602 Profile Picture
    15,404 Super User 2025 Season 2 on at
    Hi,
     
    Correct.  I don't think split screens work well with Power Automate for Desktop.

    ------------------------------------------------

     

     

    ⭐ If this was helpful, please like and mark as a verified answer to help others find this too!

     

     

    Always glad to help! 💯💯💯💯💯

     

    Tom

     

    Follow me on LinkedIn - Thomas Rice, PMP | LinkedIn

  • kinuasa Profile Picture
    795 Most Valuable Professional on at
    If the action of clicking the VBA button is skipped, I suggest specifying the Macro option in the "Run Excel macro" action as
     
    '(book name)'!(sheet name).(macro name)
    Example:
    'KK2.xlsm'!Sheet1.copy_fx_Click
     
    to execute the macro directly.
  • alee001 Profile Picture
    331 on at
    Thank you for your suggestion, but this method is only applicable to Excel files opened through processes. It is not applicable to several independently opened Excel files. It can only be executed by using the UI element recognition button.
  • trice602 Profile Picture
    15,404 Super User 2025 Season 2 on at
    Hey there!
     
    I am following up on this post there is a bug in the split excel worksheet operation. in this category power automate desktop from 01/31/2025.  I know the post is a little older, but it is a common question here so wanted to take a moment and follow-up. I see there have been 3 replies and 1 likes and asking if your question has been answered.  If so, please help the community out by completing one or more of the following actions!  Thanks in advance!
     
    Easy as 1-2-3 ‼️💯⭐😎🆒🙏
     
    1) Mark a reply as a verified answer - this is essential, and it helps others with the same general question find this thread. ✅
    2) You can also mark one of more replies as a verified answer.  Please take a moment and give the author credit for volunteering their time. ✌️
    3) Like one or more replies.  Kudos always greatly appreciated! 👍
     
    Pro tip:  if you found your own solution or workaround, feel free to add a reply to your own post and mark it as the solution too!  The goal is to get this thread marked with a verified answer by anyone that finds one or more replies helpful!
     
    Again, thanks in advance for reading and responding, always glad to help!  Tom 💯💯💯💯💯
  • trice602 Profile Picture
    15,404 Super User 2025 Season 2 on at
    If I can help with anything else please let me know or tag me in a future post, I enjoy reading and answering questions.  Always glad to help!  Tom 💯💯💯💯💯
  • alee001 Profile Picture
    331 on at
    The problem has not been solved yet, it may be a problem with different versions. I hope it will be fixed in the next update.
  • Suggested answer
    eetuRobo Profile Picture
    4,204 Super User 2025 Season 2 on at
    I would try whatkinuasa recommended.

    Although I think you run the Excel macro by just giving the name of the macro to the action (and the excel instance). Like so:


    Since you need to get the excel to be an Excel instance then try these methods:

    Method 1
    Is the file always KK2.xlsm? If so try using "Attach to running Excel" -action to attach the 


    Method 2
    If the name changes try to get it dynamically into a variable with "Get details of window" and get window title from the Excel window.


    In this case there needs to be only one Excel open and you need to change the excel UI selector to not reference any name but just Excel process. This way the Get details of window -action does not try to find an excel window with specific name but just process EXCEL


    Method 3
    Usually when excel opens it is downloaded temporarily inside C:\Users\YourUser\AppData\Local\Temp\

    The path might be: C:\Users\YourUser\AppData\Local\Temp\KK2.xlsm

    Close excels with terminate Terminate process -action and use Launch Excel to the path: C:\Users\YourUser\AppData\Local\Temp\KK2.xlsm
  • alee001 Profile Picture
    331 on at
    Since UI elements can only recognize visible buttons, I need to set the cell back to the position where the button is visible, but PAD still cannot execute the buttons of the split window. This may be its defect?
     
    Supplement:
    Unless you are the author of the VBA file, others cannot execute the button through macros. They can only execute the button through UI elements.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 525 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 324 Moderator

#3
abm abm Profile Picture

abm abm 232 Most Valuable Professional

Last 30 days Overall leaderboard