Redshift Data source Visualization works in Desktop, not when published

[Anonymous]

I have a report which connects a data source to our Redshift datawarehouse and reads a view.  The data visualisation works when in PowerBI Desktop.  But when I publish the report, check the data source against the Gateway is correct the published report shows an error.

Visualisation in Desktop:

Visualisation (published):

Error (See details):

I've checked the permissions on the DWH and that the Gateway is configured correctly.  Not sure where to go in fixing this?

[Anonymous]

Thanks to Support, we have found the issue/bug that is causing this data visualization in PBIS.

The issue is caused because we are using Redshift Spectrum to extract data from an S3 bucket and using Glue to import into Redshift.  The default schema created for Redshift uses data types 'String' - which is where the issue lies.

The initial confirmation of this was that I changed this data query from 'Direct Query' (From Redshift) to 'Import', which we could do because the dataset is small at present.  Importing the data and PowerBI must change the data to Varchars, because the issue was resolved immediately and the visuals are working once published.

This is not a long term solution as our dataset will grow.  I am now going back to Spectrum and changing the data source types from String to Varchars, which should have the same effect, allowing us to Direct Query from Redshift, as intended.

[amitchandak]

@Anonymous , Check there are few setting given in the middle of the post after publish

https://powerbi.microsoft.com/en-us/blog/announcing-support-for-amazon-redshift-reports-in-the-power-bi-service/

[Anonymous]

Thanks Amit.  I did read that post as part of my research into this issue.

When I review the dataset for the report the Gateway connections are set correctly and status 'Running' and the Data Source Credentials are all set to (admin has granted access, credentials are not required).

It must be a permissions issue with connecting via the Internet.  I'll have to keep investigating.