I don't think it's a licensing issue but I may be wrong here.ĭoes anyone have any suggestions? If I can't get this to be consistent then I need to rethink my architecture as were a small outfit and I was going to manage flat files within OneDrive. My license is Office 365 E3 so OneDrive is included as an app. * Copying the direct URL to the file from my OneDrive application * Signing in as basic instead of organizational I've tried all the steps I could take to troubleshoot from my research. Now I'm getting a completely different error while attempting to open the OneDrive browser window to select my appropriate data source. I figured the issue was having a OneDrive and On-prem gateway sql source in my data flow, so by breaking them into separate data flows and then merging them into a singular model I was able to by-pass the issue. It was giving me a completely different error message than what I'm experiencing today. This has really been bothering me lately - last week I was able to create a data flow with an excel file in OneDrive as it's source.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |