cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
FinanceBI Frequent Visitor
Frequent Visitor

Switching from Query Editor capitalizes random letters

I recently automated SalesForce data entry using Power BI. However, I'm running into an issue where Power BI will turn some of my text into capital letters, this is only happening to the last letter. The strange thing is that the text maintains it's original format within the query editor (even on the last step), but when I switch to the visual/table view some of the last lowercase letters changes to uppercase. 

 

I've already tried splitting the columns and it will still do this to the same letter regardless of whether or not the letter is in its own column. 

 

This appears to be happening to data sets that have been grouped together. I ran into another issue when I grouped items where things wouldn't merge correctly. I found an easy workaround for that issue. This one doesn't seem to have such an easy fix.

 

I read another post stating the developers intended it to work like this, but I don't think that would apply to this situation as the format only changes when I switch out of query editor (meaning it doesn't happen after any given step). 

 

Thanks for your help

 

Chris

 

1 ACCEPTED SOLUTION

Accepted Solutions
FinanceBI Frequent Visitor
Frequent Visitor

Re: Switching from Query Editor capitalizes random letters

Thank you for the response! Perhaps my question wasn't 100% clear. 

 

I'm running into an issue while trying to build reports in Power BI with data that uses a Case Sensitive unique identifier, specifically SalesForce Data. 

 

After doing more digging I discovered that this is working as intended. Power BI uses a Case Insensitive language. Upon closing the query editor Power BI will convert some letters to uppercase, the last post on this subject (2017) with a reply from Power BI developers confirmed that this is working as intended. 

 

For anyone running into this same problem, I have found a workaround and long-term solution.  

 

Work Around

One simple workaround is to create a numerical unique identifier for all data before uploading into Power BI. After extracting it from Power BI you can use the created Unique ID to merge the data from Power BI back into the original spreadsheet. This should solve this particular problem for anyone trying to automate data entry in SalesForce. However, this is non-ideal as it requires us to pull the data out of Power BI and perform one more step on it. 

 

Long-Term Solution

Apparently, SalesForce has a Case Sensitive (15 characters) and Non-Case Sensitive (18 characters) unique identifier for all objects. Unfortunately, I built out my dashboards using the Case Sensitive Unique ID, but if you were aware of this issue beforehand you could build out your dashboard building the Non-Case Sensitive Unique ID. 

 

I plan on using my workaround until I have time to alter my reports using the long-term solution. 

 

 

View solution in original post

2 REPLIES 2
Super User
Super User

Re: Switching from Query Editor capitalizes random letters

Hi there Have you looked at adding in a final step which would Capitalize Each Word in the Query Editor? This can be done by right clicking on the column, select Transform and then "Capitalize Each Word" I am certain that should resolve your issue?

Did I answer your question? Mark my post as a solution!
"Proud to be a Datanaut!"
Power BI Blog
FinanceBI Frequent Visitor
Frequent Visitor

Re: Switching from Query Editor capitalizes random letters

Thank you for the response! Perhaps my question wasn't 100% clear. 

 

I'm running into an issue while trying to build reports in Power BI with data that uses a Case Sensitive unique identifier, specifically SalesForce Data. 

 

After doing more digging I discovered that this is working as intended. Power BI uses a Case Insensitive language. Upon closing the query editor Power BI will convert some letters to uppercase, the last post on this subject (2017) with a reply from Power BI developers confirmed that this is working as intended. 

 

For anyone running into this same problem, I have found a workaround and long-term solution.  

 

Work Around

One simple workaround is to create a numerical unique identifier for all data before uploading into Power BI. After extracting it from Power BI you can use the created Unique ID to merge the data from Power BI back into the original spreadsheet. This should solve this particular problem for anyone trying to automate data entry in SalesForce. However, this is non-ideal as it requires us to pull the data out of Power BI and perform one more step on it. 

 

Long-Term Solution

Apparently, SalesForce has a Case Sensitive (15 characters) and Non-Case Sensitive (18 characters) unique identifier for all objects. Unfortunately, I built out my dashboards using the Case Sensitive Unique ID, but if you were aware of this issue beforehand you could build out your dashboard building the Non-Case Sensitive Unique ID. 

 

I plan on using my workaround until I have time to alter my reports using the long-term solution. 

 

 

View solution in original post

Helpful resources

Announcements
Ask Amanda Anything Q&A

Ask Amanda Anything Q&A

Learn the answers to some of the questions asked during the Amanda Triple A event.

October 2019 Community Highlights

October 2019 Community Highlights

October was a busy month in the community. Read the recap article to learn about some of the events and content.

New Solution Badges

New Solution Badges

Two waves of brand new solution badges are coming! Read the article for more information on our new community badges.

Analytics in Azure virtual event

Analytics in Azure virtual event

Experience a limitless analytics service built to ingest, prep, manage, and serve data for immediate use in Power BI.

Users Online
Currently online: 6 members 3,697 guests
Please welcome our newest community members: