Hi,
I am trying to "Get data from Excel" in the Power Apps website throught the Dataverse/Table page, but some columns are not visible during the mapping sequence. Here the sequence that I do (simplified version, but doesn't work either ways):
Result: In the left columns, the Document Number field is listed but not the WBS Element field, so it cannot be mapped to anything in the Excel file. I choose the "All columns" filter to be sure to not miss anything, but still doesn't show my WBS Element field.
Picture of the Table columns and the "map columns" view.
Am I missing any steps there or is it actually a bug in the interface?
Hello ALL,
am getting below error while clicking on import.
Type=Microsoft.Dynamics.Integrator.Exceptions.IntegratorClientException, Msg=Unable to parse import file d2cadc879e974fa1b543e9bd2e8441f8.xlsx Error details PQOnline failure - Type=System.Net.WebException, Msg=The remote server returned an error: (400) Bad Request.
Hi ALL,
I was able to create table with import data from excel outside my solution. It took default publisher. I then added that table to my solution but unable to update publisher.
Please suggest how to go forward
Hi ALL,
I tried to log out and login for multiple times.
Also excel has data for all coulmns still I dont see them
This fudge worked a treat for me so thank you - the Export failed (my table was empty anyway) but once I returned to the Import, my new table structure was reflected correctly.
It seems a simple solution for Microsoft to refresh whatever data the Import is relying on when a table is amended in any way - critical for such a fundamental function such as a data import you'd have thought.
At least the faux Export trick worked for me, so onwards and upwards...
I've add this problem in the past and had it once again yesterday.
First time i had it, playing around with creating a dummy row and possibly waiting around for some time worked.
Second time, i threw multiple solutions at the wall, screamed a little bit and it worked...
But yesterday, the issue was more persistent... Finally, exporting the current table with the missing columns in excel and then trying the import from excel again seems to have updated the import with the new columns!
If that doesnt work, perhaps doing the steps above but first marking the missing columns as required.
You'll then be able to change them back to optional.
Thiis^^^^^!!!!!!
Microsoft needs to start refunding the license fees. It's not fit for purpose. It's a complete joke.
I give up. I've spent half of the day trying to get this to work. I could have built 10 SQL Server databases and imported data from dozens of files in the amount of time I spent trying to import TWO columns from Excel into one new Dataverse table. Columns don't show up, edit data in Excel and pasting 10 rows of data causes over 1000 table updates according to the plug-in. This is insanity. Importing data is database management 101, and every tool out there is simple and basically the same in my experience - (1) clean data, (2) identify source, (3) identify target, (4) map columns-->done. But whoa! Not this half baked piece of junk. We have to clear out cache, sign out, reboot, go on holiday, take a sabbatical, etc. and it MIGHT work when you get back. Microsoft is cramming Dataverse down our throats and selling premium licenses like crazy but they can't afford to get product developers who can make such simple utilities work. FRUSTRATED.
Thank you @stevenhsi
I have saved this solution and will give it a try when I can get back to it.
(-:
Although this workaround may work for some people it seems like it doesn't work for others, so I would only consider this a partial solution.
1. Go to the homescreen in make.powerapps.com
2. In the second section of the left navigation bar, open Connections. If you can't see it, click on ". . . More" and select it from the flyout.
3. Look for the Microsoft Dataverse connection and click on the ". . ." next to it.
4. Select "Delete". It will give you a warning of any flows that use this connection. You can re-add it later.
5. Once deleted, clear your cache/cookies/browsing data for the powerapps website and/or any other microsoft related website just to be safe.
6. Open make.powerapps.com and go back to Connections, and add Microsoft Dataverse as a new connection. You can search in the top right for it to save you some scrolling time. Use your usual login and wait for it to reconnect.
7. Wait a couple minutes.
8. Go to the table that you want to Import From Excel to and try to do the import procedure again. You might get an error after uploading the file that the mapper is unavailable. This is a good thing, as it means that it is still processing the reconnection that you did in previous steps - if this happens give it a couple more mintues and try again.
This step by step process worked for me and now the columns that I had added after the first import are now listed as mappable columns.
I hope this helps someone else, or at least some variation of it.
I think it cached on the first import attempt as mentioned by other users hence, it is important to create all the columns before using the import wizard. Subsequent adding or removing or columns is not expected to work.
Abide by the following:
WarrenBelz
791
Most Valuable Professional
MS.Ragavendar
410
mmbr1606
275
Super User 2025 Season 1