missing records, update excel table then send out and delete

(1) Share

Report

Posted on by joeytsui

hi All,

I have a recurrence flow to get rows from an on-premise sql server view, and write it to an excel table locate in onedrive business, then send it out by email, then clear all data in the excel file for next time use.

i got some problem on the below flow.

1) i get the rows from sql server view is 270 rows, and added 270 rows into the excel table. However, when i send it out by email, the attachment only contain 158 records. then i add a delay 15sec after [add a row into a table]

it contain 201 records. it's look like i need to wait some time after update. May i know how much time i need to wait after update ?

2) after send out the file, i want to clear all data from the excel table, but it's always remain some reocrd in the file. like below flow, the records in the file is 270, but the step [Delete a row] only process 256 records

pls help, thanks in advance.

Categories:

Business Process Flows

All responses (1)

Answers (0)

ivan_apps 2,187 Super User 2025 Season 1 on at

Like (0)

Report

missing records, update excel table then send out and delete

I’ve never had to encounter a delay when writing to excel files. Maybe you are experiencing a different issue and adding a delay is just a random coincidence? There is an automatic limit when retrieving rows from a table in excel, i believe it was 250, but you simply would just have to modify the settings in the action to increase the paging count to 1500 or something higher. Perhaps something in the action’s config is giving you bad readings.

for your second issue - what i would recommend is to create your ‘template’ file with no data. Your power automate flow should copy this file and save it under a different name. Populate this new file with your data, send it out and you can either delete the entire file or keep it for archival purposes. Your next run should just copy your template again without having to delete rows at all. This way your template’s integrity is kept when random issues happen, they wont affect the next flow run.