I like to update an excel row as the result of a twitter search. (Microsoft Flow)
When I choose the correct excel file from my onedrive I get the message "No items" when I want to choose an excel table.
I have two tabs in the excel sheet. In one tab I have named the rows on the top.
What could be wrong? I have no idea.
Or what do they mean with excel table? Isn't a tab meant?
You actually need to add a "Table" in excel for it to be usable by PowerApps. Here are some steps for that:
Create the tab in excel, and add the column headers as you probably already have, then select them all.
In the "Insert" tab, select "Table"
Make sure to select the "My table has headers" option, and click OK
At that point, you have a "table" created in excel. You can change the table name in the design tab (highlighted above) - in my example I will rename it to "PowerAppTweets".
Now you can use that table in your flow, as in the example below.
Hello, I'm another human attempting to use your product. I am getting the same problem here, but unlike the OP, I understand what a table is and have been using an xlsx spreadsheet with a table in it. The table is called Table1 but the "get rows" connector consistently crashes during Flow execution saying it can't find Table1. Interestingly, the part of the flow that refers to the column names of said table does indeed pull the correct column names and allow me to use them when creating a SharePoint item. This is such a frustrating experience. A SharePoint list is literally modeled on an Excel table to some extent, yet here I am trying to do something VERY simple and it's just brick wall after brick wall. I have recreated the spreadsheet multiple times, I have tried different column names, I have even rebuilt the stupid Flow. I'm about to give up and go talk to my boss about maybe finding another solution for this automation process. Thanks, MS!
So does that mean, to work with the Flow | Excel connector, you have to open and edit the Excel file at least once? In my opinion, this destroys the purpose of this connector.
Use case is as follows: Weekly, we get a mail with an excel attachement. We want to extract data from this excel file and process this data to be displayed on a SharePoint site. This should be a fully automated process.
The problem is, if you just use a generic "when file is uploaded" OneDrive connector or whatever, along with a generic "get rows" connector that points back to the OneDrive connector's File ID field or whatever it's called, how do you find out what the columns in the Excel table are as you are editing the Flow? It can't know what the valid columns are until the Flow actually runs and looks at the file. You can use the "expression" tab in the dynamic data thing that comes up and type body('name_of_connector_that_gets_rows')['ColumnName'], and you can make it easier by creating an excel sheet for you to use to automatically generate this for you, but it is tedious and basically just a hacky workaround. You can also use the OneDrive "when file created" connector and then use a "get rows" connector that you point directly at the Excel file in OneDrive so it can get column names for you, but this requires you to put the file in that OneDrive folder as you are editing your Flow so it can get the column names so they'll show up in dynamic data later on in your Flow editing process. But then if you go back to try to edit your Flow later and the Excel file isn't there for some reason, the column names might not show up. It's pretty silly. In my opinion they need a connector that just lets you enter Excel column names of your choosing to use as dynamic data later on, but then such a connector would have no actual knowledge of the rows in the Excel table. The whole thing is not very well thought out on their part IMO and touted too heavily in the community as an "easy" thing to do. Pretty par for the course with this product if I'm honest. 😕
I'm constantly getting the next error message and can't find anything on the internet about it:
"Could not retrieve values. Failed to get dynamic values"
@McRoe Try to convert the excel table to range (Table Design, Tools, Convert to Range), and then range back to table. That solved the issue in my case.
Stay up tp date on the latest blogs and activities in the community News & Announcements.
Mark your calendars and join us for the next Power Apps Community Call on January 20th, 8a PST
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!