* * UPDATED

Later in the course you showed the Table properties, and I was able to fix my problem there. Even though the preview shown when importing from an external excel file indicated that all columns were selected, they weren't, and this was shown (and fixed) using the Table Properties options. Not sure that it fixes all the issues, but good enough for now.

* * ORIGINAL posting

Power Pivot & DAX Course (2016) using Office365

Lesson 3.05 - Importing data from external excel files.

I followed your instructions for bringing data in from an external table for the Dates table. When you extended the example to add the new column for Month Name (Lesson 4.03), my table did not update with the new column. It says it is successful, but nothing changes.

I think it's a bug because:

A couple of times (but not always) it would run the refresh even though the source file was open.

It WILL show the update for additional ROWS. I added 31/12/2012 for a total of 1419 rows, and that appeared after a refresh.

If I go to Existing Connections and right click on that connection (to the Dates source file) and select Open, it will load an additional tab/worksheet to the model, Dates1 (auto named) showing the new column. And I can delete the original Dates tab, and rename the new one back to Dates, but that's not really going to work once the model is finished.

I added an additional column (to those mentioned) with filler numbers (1,2,3,4) repeating down the column. I got that column to appear in the model using the Open (from Existing Connections) and adding a new tab Dates2 but the column was filled with the number 1 only, all the way down. The preview showed the correct numbering, but something happened during import (I assume).

After a refresh (I kept trying), it added Columns named F9, F10, F11 with nothing in them.

My first attempts were with the source file on an external hard drive, so I copied it to a location on the C Drive, but no different (long shot).

Loving the course. I will eventually be using this to access files in sharepoint which I will do through Power Query, so this bug is just a nuisance... and I will battle on, but if you have any thoughts, I would love to hear them.

Thanks and cheers Donald