The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I'm a PBI newbie, so I was thinking here.
I have an API that calls around 15 columns and they're all related.
Company / Last Update / Lead Status / Company Size / etc....
When I load the API I get all colmuns.
It's better to divide them into various queries and them "relate" them?
Or import all the columns into only one query?
Hi @Anonymous
Then just use 1 query and do your transformations on the data returned. If you need assistance with the API calls or anything else, just post back here.
regards
Phil
If I answered your question please mark my post as the solution.
If my answer helped solve your problem, give it a kudos by clicking on the Thumbs Up.
Proud to be a Super User!
@Anonymous
It depends, If all the columns are related to the company (entity), it's better to keep them in one table. If you have company and other related data are all in one table it is advisable to separate into different queries
________________________
If my answer was helpful, please consider Accept it as the solution to help the other members find it
Click on the Thumbs-Up icon if you like this reply 🙂
⭕ Subscribe and learn Power BI from these videos
⚪ Website ⚪ LinkedIn ⚪ PBI User Group
Hi @Anonymous
I'd just make 1 query and get all the data at once. Though I'm not entirely sure what yu mean by the 'API calls around 15 columns'? It returns 15 columns?
Phil
Proud to be a Super User!
Yes! Returns me around 15+ columns after I "open" the Records