Power Automate

power automate with excel refresh

(1) Share

Report

Posted on by SR-13011330-0

i have 2 dataexcel server,xls monitor.xls coming in mail excel each with 25 k rows

my requirement is to compare two excel and find server list which are not part of monitor excel.

i created

1. save server excel in sharepoint . and run power script to drop & create a table

2. save monitor excel in sharepoint . and run power script to drop & create a table [as import via PA is slow and limit ]

3. have exceptions file with exception sheet to exclude in reporting

4. copy server list and monitor list sheets into exception file and compare and report extention.

while running. as there is drop table . flow have hardcoded table into id and throws table not exist . how to over come this issue

Categories:

General topics

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

11manish 3,849 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

The root cause is that Power Automate caches the Excel table metadata. When your Office Script deletes (drops) the table and recreates it, the newly created table gets a new internal Table ID, while the Excel actions in your flow still reference the old ID. As a result, subsequent actions fail with "Table not found" or "Table does not exist."
For your scenario (two Excel files with ~25,000 rows each), do not drop and recreate Excel tables. Keep the tables permanent and only clear, repopulate, and resize them. If the comparison logic becomes more complex or performance is a concern, move the entire comparison into an Office Script, letting Power Automate orchestrate the process rather than process the data itself. This is the most scalable and maintainable solution.

1 people found this reply helpful.

Was this reply helpful? Yes No
SR-13011330-0 9 on at

Like
a
(1)

Report
Copy link

Link copied!

thank you for quick response . i moved entire action of creating table, comparison all into office scripts as i got performance.and "in use" errors . drop and recreate step also due to that . let me try now

Was this reply helpful? Yes No
Suggested answer

Valantis 7,006 Super User 2026 Season 2 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @SR-13011330-0,

Moving the entire comparison into a single Office Script is the right call for this scenario. At 25k rows each, doing everything inside the script avoids the Power Automate connector overhead, the table ID caching issue, and the "in use" conflicts that come from multiple connector calls hitting the same file.

The script handles the data natively in Excel's memory which is significantly faster. Let us know how it goes!

Best regards,

Valantis ✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/ 💼 LinkedIn ▶️ YouTube

Was this reply helpful? Yes No