Forum Discussion
Resolver ITables appearing where they're unwanted
1. Starting about a month ago (or so), I started noticing that when I import a lakehouse table into the dataflow as a source, I see other tables in the list of table columns (schema view). These tables are linked to this source tables in the model but they are unnecessary for my purposes and I have to remove them.
2. The following image shows a table in the column listing in the data destination wizard. Again, this is an unwelcome recent occurence. In the dataflow UI, the schema view would not show the Job table as a column.
Is this expected behavior going forward? Or is this a bug? Something doesn't feel right.
Hi ebjim
Apologies for the issue you have been facing.
If its a bug, we will definitely would like to know and properly address it. Please go ahead and raise a support ticket to reach our support team: LinkAfter creating a Support ticket please provide the ticket number as it would help us to track for more information.
Thanks.
Hi ebjim,
let me answer to your points:
1. if your source Lakehouse table has relationships with other tables (e.g. foreign keys), it is normal that the linked tables are shown both in the Data view
and in the Schema view
2. seeing the linked tables in the column listing of the data destination wizard was instead a bug which has been fixed. Please try the scenario again and let us know if you have any additional questions
6 Replies
AlvenMicrosoft Employee
Hi ebjim,
let me answer to your points:
1. if your source Lakehouse table has relationships with other tables (e.g. foreign keys), it is normal that the linked tables are shown both in the Data view
and in the Schema view
2. seeing the linked tables in the column listing of the data destination wizard was instead a bug which has been fixed. Please try the scenario again and let us know if you have any additional questions
- Element115
Memorable Member
Something similar briefly happened to me as well and then was gone. I think what's going on is that the backend is probably too complex with too many moving parts. When the engineers fix one bug, they break something else, which happens. I know, when I was working as a software engineer it happened more often than not. I just hope the codebase isn't a huge spaghetti ball because otherwise we'll be facing issues for years to come. In any case, I don't understand how Microsoft can claim Fabric is GA ready. Not!
ebjimElement115 I agree with your thinking about GAing too soon. There are some very fundamental changes between Azure and Fabric.
Hi ebjim
Apologies for the issue you have been facing.
If its a bug, we will definitely would like to know and properly address it. Please go ahead and raise a support ticket to reach our support team: LinkAfter creating a Support ticket please provide the ticket number as it would help us to track for more information.
Thanks.
Hi ebjim
Thanks for using Fabric Community.
I tried to repro the same but didnt face any issue as mentioned above. I think this is an intermittent issue. Can you please try to do the same after a day or two? If the issue still persists please do let us know.
Hope this helps.
