Forum Discussion
more location data required?
So I figured out the issue, apparently the field literally has to say Zipcode. Before it worked with a business logical named of Job Zip (referring to the zipcode of the vendor job for my data) But when I fixed my cube's dimension attribute to zipcode and works great now.
I know that makes perfect sense but why did it work with a different name in the preview and then get so specific in the release? Seems like a step backwards.
CJenner you can also click on the field in the Desktop and then click on Modeling->Data Category->Postal code. This will help your model understand the granularity of your geography.
It had nothing to do with the model or granularity, it had to do with the fact it worked in Preview but when they did the release they got specific. So unless you specifically labeled the Dimension attribute, or table attribute, Zipcode instead of say "Zip City" it wouldn't work. That is a big miss. Maybe my business unit doesn't want it called Zipcode or Postal Code. Maybe they want it Zip City. So to me, that's a fail because a true Dimension model (ala Kimball) is based on Business Process and what the business calls it, not what the application wants it to be.
it doesn't matter what you call it if you read and follow my instructions above.
I have a similar issue however power bi will plot some but not all of my zipcodes. For example it will work fine in California, but not plot an zipcodes in Illinois. Any idea as to why it will not plot certain zipcodes?
