Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
I have some excel files that are posted on a sharepoint folder every morning. Each one contains information about product shipments. Each file tracks a particular product. So maybe some units of product A was shipped to several locations.
Unfortunately, the legacy system these files come from put the product and a couple of other "superheader" type information into cells in the top row of the table, creating a superheader.
I have been able to get them to load, and using the first file as an example, I promote the first row as headers. This gets rid of the superheader row in the example file. However, when the query tries to fetch other files, it looks for the column that had the product information in it and gives me an error saying "field 'product A' not found".
I had thought that by removing the superheader in the first file, it would do that for every file BEFORE it tries to combine them. That does not appear to be the case. It seems that my only option is to try to get the users to delete that top row before they post to the SharePoint.
It doesn't seem that it would be a huge leap in technology to make this happen. Am I doing something wrong, or does the function just not work in the right sequence?
Solved! Go to Solution.
I got it to work! It turned out that PQ added its own promote headers step, followed by a type change step. Maybe that's because the files I have to work with have a blank row at the top, then the super-header, then the headers. In any case, that change type step is looking for the text in the superheader as it tries to emulate the code in the example file going forward. I eliminated that change type step, added another promote headers step, and it worked like a champ!
I got it to work! It turned out that PQ added its own promote headers step, followed by a type change step. Maybe that's because the files I have to work with have a blank row at the top, then the super-header, then the headers. In any case, that change type step is looking for the text in the superheader as it tries to emulate the code in the example file going forward. I eliminated that change type step, added another promote headers step, and it worked like a champ!
"Promote headers" turns the top row into column names, so if you have inconsistent text in the top row of each file, then you'll get inconsistent column names, resulting in errors when trying to combine the files together.
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
34 | |
30 | |
18 | |
12 | |
8 |
User | Count |
---|---|
50 | |
35 | |
30 | |
14 | |
12 |