Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM. Register now.

Reply
sonaliverma
Advocate I
Advocate I

Change the data source from SQL server to Amazon redshift

Hello Everyone,

 

I need to change the data source in PowerBI from SQL server to Amazon redshift, But all the columns in Amazon redshift are in lowercase, and on SQL sever it is in another case.

 

When I changed the data source, I lost all the fields in the visual and it is showing an error. I need to again take the fields in the visual.

 

Could you please suggest any method?

 

 

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Hi @sonaliverma ,

 

Yes. I have created a test to reproduce such scenario.

1.Connect to Excel file1 with uppercase column names and then create visuals.

2.Replace Excel file1 with  Excel file 2 which column names are lowercase.

3.Handle errors in Power Query.

4.After applied changes, the visuals are needed to fix.

Eyelyn9_2-1649641801913.png

 

 

Eyelyn9_1-1649641788479.png

 

I think it's the expected output since the visuals could not find the fields any more.

 

And according to my researching, you could firstly change the column names to uppercase before you do any transformations by using :

RenamedColumns = Table.TransformColumnNames(Source, Text.Upper),

Then you don't need to re-arrange the vsiuals.

 

 

Best Regards,
Eyelyn Qin
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

It's an expected behaviour.

View solution in original post

1 REPLY 1
Anonymous
Not applicable

Hi @sonaliverma ,

 

Yes. I have created a test to reproduce such scenario.

1.Connect to Excel file1 with uppercase column names and then create visuals.

2.Replace Excel file1 with  Excel file 2 which column names are lowercase.

3.Handle errors in Power Query.

4.After applied changes, the visuals are needed to fix.

Eyelyn9_2-1649641801913.png

 

 

Eyelyn9_1-1649641788479.png

 

I think it's the expected output since the visuals could not find the fields any more.

 

And according to my researching, you could firstly change the column names to uppercase before you do any transformations by using :

RenamedColumns = Table.TransformColumnNames(Source, Text.Upper),

Then you don't need to re-arrange the vsiuals.

 

 

Best Regards,
Eyelyn Qin
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

It's an expected behaviour.

Helpful resources

Announcements
FabCon Global Hackathon Carousel

FabCon Global Hackathon

Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!

October Power BI Update Carousel

Power BI Monthly Update - October 2025

Check out the October 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors