The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
Very random question.
When I import tables from SQL, BI is including columns for other tables not requested. The system we use (JobBoss) was upgraded on Friday and there are changed to the tables in my data model. These changes cannot be seen in SSMR so the connections appear to be generated by Power BI.
Has anyone seen this and can they be switched off? It's possible they are useful connections and I sometime merge the specific tables together but I can't have the data model changing itself when our system goes through an upgrade.
For example SO_Header is a separate table to SO_Detail. Crystal shows them separate, Power BI included the Detail table when the Header table is imported in isolation.
Help please.
Solved! Go to Solution.
Try clearing the Include Relationship Columns setting:
Proud to be a Super User!
Excellent, that does seem to be the problem. Do you know how I can switch that off for existing models where that has been selected?
THank you
There may be an external tool that will allow you to change that setting. Otherwise, you'll have to manually change it in each model.
Proud to be a Super User!
Try clearing the Include Relationship Columns setting:
Proud to be a Super User!
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.
User | Count |
---|---|
111 | |
80 | |
78 | |
43 | |
37 |
User | Count |
---|---|
158 | |
111 | |
64 | |
59 | |
54 |