Here's our use case and how we're trying to cope with this issue.
Hopefully the notation is self explanatory!
Original Dataflow:
Forms UI -o-> Excel -o-> PowerBI
Current (Broken) Dataflow:
Forms UI -x-> Excel -o-> PowerBI
Temp Workaround:
Forms UI -?-> Excel -o-> PowerBI
\ /
o o
\ /
Power Automate
Alert with link
to open Excel
and trigger sync
Resolved Dataflow:
Forms UI Excel -o-> PowerBI
\ /
o o
\ /
Power Automate
Excel update
The latter is not ideal as:
- it requires breaking the sync function by disassociating the Excel used for the sync and the one used for the Power Automate/PowerBI workflows, as the sync isn't smart enough to realise the data's already added via Power Automate and would otherwise result in duplicate data.
- it's high maintenance to develop and maintain with a large number of columns - overall more fragile than what we originally had.
It could be resolved if Microsoft could add a new Power Automate flow/function that just triggers their new Forms-Excel sync function without the Excel file having to be opened.