Forum Discussion
Paginated Reports Geospatial Data Issue in Service?
Hi
I am trying to transfer over an SSRS report into a paginated report to run on the Power BI Service. I have migrated a bunch of SSRS reports to Paginated, but the one I am stuck on uses a map. It has an SQL datasource, which has a geography field that looks like "0XE610000000010C51DD............". The report runs on our SSRS server, as well as our Power BI Report Server, but when I upload it to the Power BI Service, I get a lengthy "Null Key" error, but none of the keys are null. I have tried taking out the map, and just putting an expression to pull the first "Geography" field, and it still gives me the same error. As soon as I get rid of the geography field in the report, it works again. Would anyone have any insights into this?
2 Replies
No insights, but this might be a good one to file an issue for. Migration from on-prem to service we are trying to make as seamless as possible for all the supported features.
It's because PowerBI gateways don't support complex data types of which geo is one. There's no published solution except to use a map visualisation in a regular powerbi report with lats and longs instead of geo data. OR use an azure database which doesn't require a gateway.
