Excel table not being added properly

[BaldgytAgain]

Trying out powerapps:
l have an excel sheet on my business one drive with a single table of 17 columns and 134 rows. When I connect it to an app either manually or via the create Omedrive phone app wizard I get a connection, it picks up the field names (column headings from the table) but I get no error but I get no data.
I notice that no _powerappsId_ column is created in the sheet.

I have tried renaming all the columns to simple text (no spaces)
I have copied the data out of the sheet into a new sheet so that there is only a table. but no luck. Other small test tables seem to work.

(There is also some odd lag going in that If I create a new table on my web view of one drive - say by copying it does not appear if I try to connect to it from an existing app. I assume this is a known thing but. I do have a lot of data syncing going on).

Is there a place where I might see an error message e.g. a log from the wizards or something from the connector?

[BaldgytAgain]

No - that was the point of my original point. There is no error message the app has no alerts it just doesn't show any data and the column is not added to the table.

Hence, my asking if there is any kind of log which might give information e.g. from the wizard.
The fault seems to occur with newer and.or slightly larger tables.

[Drrickryp]

Hi @BaldgytAgain and @eka24 

I downloaded your file and got the same result that you did.  It wouldn't import the data.  I took the file as is and exported it to SharePoint then created the app with the SharePoint connector and it worked fine.  Then I exported the SharePoint data back to Excel and created a new app from the Excel connector. In the pictures below the order and the labels are reversed.  The first picture is from the SharePoint data imported back into Excel.  The second picture is the SharePoint connector from the original Excel file downloaded from @BaldgytAgain SharePoint file from original Excel exportOne drive excel file from SharePoint export

I have no idea why this worked!  Perhaps better minds than mine can figure it out.  In any event, "washing" the data through SharePoint proved to be a work around for this problem.

[BaldgytAgain]

@Drrickryp 
Thanks
Thanks. I also have a version that works fine in a SharePoint table which I made some time ago by importing the Excel sheet like you. (So you may wonder why I care about Excel and one drive)
{I hadn't considered making a new sheet from that  so that's interesting)
Unfortunately, we are small-town council (I was mayor) and they have little technical skill. We have one member of staff who has a bit of an idea how to use Excel and is one of those types who once they know how to do a bit with something just keeps using it. My view that if you don't need to calculate anything you shouldn't be using Excel has not worked and she declared Sharepoint "too hard". So in order to get some cloud-based stuff going, I relented and they put their Excel sheet on one drive with links to other files overdrive and share that with councillors which has worked well enough for our face to face meetings. Now we are in lockdown and they are sending out documents to everyone to fill in and I thought I'd revisit an app.
I wondered if it was the fields linking to other one drive documents in some columns but I think I tried removing them and it still failed. (I probably should have made more notes - but I had no idea it was goign to be this hard)
I had a look at the sheet and I couldn't see any oddities - the person involved in addition to using a spreadsheet when she shouldn't - also tends to create them like it's the year 2000 - but I can't see anything unusual.  And I have just noticed that the creator of the sheet is someone which I never heard of and doesn't work there - so it may have been cobbled from parts - perhaps it started life in a much older version of Excel?
It's great to know that it failed for you (if you see what that means) - in that it suggests that it isn't my environment that is broken (I have nearly finished a 200Gig upload of virtual machines from my years as a trainer at Microsoft - platforms and networking) so I wondered if the excessive load was part of my problem (being throttled somewhere perhaps).
I'll keep playing but thanks for trying it rather than just assuming that I didn't know how to do it at all.

warning: it's probably just me getting "punch drunk" but I am beginning to suspect that once an environment has failed with this sheet further attempts to create connections through one drive to other spreadsheets (that work in other environments) no longer work - almost as though it has "poisoned" the connector. I hope that isn't the case and that is messes up anything for you.

Now, if anyone out there knows if there is some kind of error log or monitoring/trace I can turn on to find out more.

[jorgep]

UPDATE:   

I tried the Start Data from  Excel Online  route (instead of the OneDrive) and it worked FLAWLESLY!   YEAH!

Hope this post save someone 2 hours of troubleshooting 🙂 Cheers!

Folks -   

I really want PowerApps to work for me, but something is  fishy here..   Any ideas?

Using the latest Microsoft Excel for Office 365 (16.0.11929.20946) 64-bit

I am having the same exact issue with my data in excel  (no formulas, correctly set tables, etc, etc, etc.) 

Basically PowerApp "wizard" it is not recognizing all of the columns  in the table...

I went back and watched the beginner videos (thanks but basic) and then I re-created manually the sample spreadsheet.   Placed it on OneDrive, waited for it to sync, exited  and ran the new PowerApp from source  on OneDrive and  got the following result 

The view screen shows all the fields but not in the same order as the table, and does not show the data values. 

Seems like the SharePoint sanitation is a a bit of a detour --  

[MarianoLazarte]

I know this is quite old but trying anyways...

Did anybody get a solution? I am suffering the same problem.

Thanks in advance,

Mariano