Unanswered

ColumnHeadersRow is returning OLD data as headers

(0) Share

Report

Posted on by OhMyJosh

I'm trying to use Power Automate for the first time to scrape a table from a website. But the headers of the table move around and completely change often. When I run the scrape on different data (Data with different headers) it's showing the OLD headers, making the whole thing worthless. I tried clearing the DataFromWebPage variable each run, but while it's setting that variable to 0 it apparently is keeping the ColumnHeadersRow in cache or memory somewhere.

I am really surprised that I couldn't find others with this issue (since the functionality is over a year old now) but I can't and I'm hoping there's a setting somewhere or someone can tell me what I'm doing wrong.

Thanks.

Categories:

Power Automate Desktop

All responses (4)

Answers (0)

Sort by

Nived_Nambiar 18,138 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @OhMyJosh

Yes that seems to be a bug

One thing you have to note is while extracting data from webpage, we are adding the column name , so i think it would keep as always
Tibobago2 2 on at

Like
a
(0)

Report
Copy link

Link copied!

I came across the same bug. I'm extracting a html table and want to save it as excel.
The ColumnHeadersRow keeps the header names from a previous extract, even if I'm using a different variable name before ColumnHeadersRow.
Is there a way to force the clearing of ColumnHeadersRow?
Nived_Nambiar 18,138 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Tibobago2

while saving datatable to excel, if i am right it won't be saving headers , so that you can insert a row at position 0 row index to insert the headers and then after insert it to excel, it become headers.
Agnius Bartninkas Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

You generally define the header names manually when you use the Extract data from Web page action. It does not actually extract column names itself. I suggest you extract those via a separate action and store it into a list that you can refer to.