Forum Discussion
Post Prodigydesktop.ini file
Hello - no, I went back to a differing pbix file (with completely different data sources, but still excel) and it worked fine. That indicates it's not a computer/compatibility issue?
As I have researched, the desktop.ini file is a windows (hidden file) within each folder. I have no idea, why this problem just popped up. But, I have gone thru and within all import related queries, filtered out this file name, and all is well....
thanks for your suggestions!
I fixed this when I noticed the .ini file was showing up first on my first step in my query rather than the file I was trying to import.
What you need to do is have another editor file where it is working, then mirror the query editor step code in the helper queries. You will have to adjust the Sample File, Transform File (invoke function), and the Transform Sample File Query.
Then your final query will expand the correct table rather than the .ini
No idea why it happens in the first place, but I only have this happen if I try to folder import from One Drive.