Flow Import Issue

[Joel01298]

I believe I have encountered the same issue as the other two individuals that have had an issue upon import. Although their error message was in another language, mine is in English and I hope that it helps with figuring out what the issue is. I am a novice at Power Bi and this is my first time using Power Automate to create a flow so that may have influenced the issue at hand. I have attached a snippet to display the error message

I copied the directions as instructed, I was going to create a test flow then once I had it figured out, then I was going to re-do the steps with the actual data that I have at hand.

[robinthakur]

I'm also getting this error at the import stage and cannot proceed. I don't believe this is an issue with the Excel file and the tables contained on it, as it doesn't get to the point where I can plug in values for where it is stored. Could Microsoft have changed the Excel Online EndPoint for 'Get Table' as 404 is pretty clear cut as 'does not exist'

[Joel01298]

Sure, I could see Microsoft making an update that could have interfered with the process of the template. Either way, I'm going to be looking for an alternative solution but if this does get patched up I'm sure it would be beneficial for individuals that happen to come across it in the future.

[robinthakur]

Yer, and if you go create a new Flow and look at the actions available through the Excel Online connector, there is only "Get Tables" not "Get Table" so definitely looks like a change here is to blame.

[scottman01]

I had the same issue. There looking at the error code, there was a message that said to save it as a new flow in order to be able to import.

Did that. Saw that every Excel connection had to be updated. Once I did that, and reconfigured everything to point to my SharePoint document folder where the Excel file was saved I was able to run the workflow successfully. It is not perfect though. It is pulling in every team and every planner that I am associated with and taking way too much time to run even though I set the filters to a specific team/plan. I am going to modify the flows to not pull all of the Teams and see if it works any better. Will update my results when complete.

[scottman01]

OK, I found that the step "List Teams" was causing the flow to pull in every team from our organization and subsequently every Planner Plan, all of the users from all of the teams and essentially more information than I wanted or needed.

I deleted the List Teams step, changed it to List Plans for group and moved everything up a notch in each branch.

The flow worked great except that it was stopping after doing 400 rows from our plan (currently over 600). So I went in to the steps List Tasks and List assignments and changed the pagination settings setting a max of 1000. Flow ran perfect!