Forum Discussion
Map visualization limits and issues
One caveat to this approach is when using Analysis Services. There does not seem to be a manual way of doing this in Power BI.
I should be able to create an ad-hoc field that combines the data I need to map properly.
I created everything as a geographic data in the cube and specified it as it's matching category (city, state, zip), but this still does not help.
You really need specific instructions on how to handle this or make BING smarter.
I'm testing another product Tableau and it handles it without any problems.
I ended up adding another field to my Zip Code lookup and structure like I would mail a letter "City, State Zip".
Ran into one rather curious issue though, I added a filter for the State and it's not making the list unique.
So I get repeated values for the state from my zip code table. I shouldn't see NY,NY... just NY. Not sure why thisis happening
I agree, tableau handles the record volume just fine (I'm dealing with about 6M+ records). I really don't want to invest a huge amount of effort building a PowerBI solution if this issue is not fixed quickly. Once you see what is possible, you don't like to have to build work-arounds. What are others using as a work-around? ~Denise
- kcwilsonii8 years agoHelper I
I can't say tableau handles the large record volumes well.
Actually had a project recently which it totally balked on. Updates to each page were exceptionally slow and building linked tables proved unusable due to the volume of data.
I had to import the into Microsoft Sql Server Developer edition and create a smaller data set for it to work.
This project was for an online class using tableau.
If I had the choice I would used PowerBI, better structure for build of your data and display and distribution to various formats
- DHoban8 years agoRegular Visitor
Hi,
Thanks for the response. I am doing a parrallel comparison. Our IT wants to use POWERBI, but I already had Tableau, so I am using tableau to proof the PowerBI results. Both are connected to the same 'normalized' table in an SQL Server database.
The result so far is that I cant even get PowerBI to include all of the results because it hits overload mode. Do I really have to create separate views to be able to create small-subsets of data? Actually... I haven't even tested if I can use views yet in PowerBI. Is that doable?
I do feel (from what I have seen so far) that Power BI might have better publishing capability (my company is in the middle of purchasing a server so that we can publish to it). That is why I need to stick with this, but it is not nearly as user friendly as Tableau. My fear is that if I can't report accurate/full summary of data, the publishing isn't going to matter.