Forum Discussion
Dataflows and "Complex Columns"
So I figured out it was because of power query transform steps that were changing a date/time column to be formatted as time only. That caused the warning and I assume created the "complex column". Once I deleted those steps the data flow was finalized and saved.
Now my problem is that when I open Power Bi desktop and try to attach to that dataflow as a source, my credentials that I have used in PBI desktop to sign in with are not the ones being recognized. It is taking me to my test dataflow that was built on a different O365 tenant space, under completely different credentials. I tried switching user and then back, still goes to that original dataflow.
So I figured out it was because of power query transform steps that were changing a date/time column to be formatted as time only. That caused the warning and I assume created the "complex column". Once I deleted those steps the data flow was finalized and saved.
Now my problem is that when I open Power Bi desktop and try to attach to that dataflow as a source, my credentials that I have used in PBI desktop to sign in with are not the ones being recognized. It is taking me to my test dataflow that was built on a different O365 tenant space, under completely different credentials. I tried switching user and then back, still goes to that original dataflow.
Figured that issue out as well by trial and error.
While the credentials you sign in with power bi desktop do not seem to change which tenant space it is looking for the dataflows, the data souce settings icon in the Power Query Editor toolbar will have a datasource listed (Power Bi dataflows) and I had to go in and edit the permissions (credentials) to that datasource directly. Then the dataflows listing refreshed with the proper tenant space dataflow.
Figured someone else may end up wanting to know that as I havent found this level of instructions available online.