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

Power BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.

Reply
Anonymous
Not applicable

type conversion function (used to remove accents) creates new errors

Hello,

I have found this function on internet to remove accents :

 

= (textToConvert) =>
let 
    textBinary = Text.ToBinary  (textToConvert,              1251 ),
    textASCII  = Text.FromBinary(textBinary   , TextEncoding.Ascii)
in    
    textASCII

 

It works fine when I look at the results of the queries but when I hit the Apply button to update my dashboards, I now get several times this error on different queries, which weren't there before I used this function : "error ole db or odbc error exception from hresult 0x80040e4e"

I also now get this error on another query : "Column 'xxx' in Table 'yyy' contains blank values and this is not allowed for columns on the one side of a many-to-one relationship or for columns that are used as the primary key of a table"

I guess I am having this issues because the function changes the type of the column.

So do you either know a better way to remove accents dynamically without changing the type of the column or how I can fix the errors I have now that I use this function ?

For the second option, is there a way maybe to store the type of "textToConvert", and then add a third convertion to g ofrom ASCII to the original saved one ?

Thanks for your help

1 ACCEPTED SOLUTION
Anonymous
Not applicable

I found the issue, Power BI had created a table relationship in my model that I hadn't asked for and it was base on an ID which had indeed one null value. So I can fix it by either removing my relationship in the model or by removing the null values in an additionnal Power Query step.

So my function to remove accents is OK.

View solution in original post

1 REPLY 1
Anonymous
Not applicable

I found the issue, Power BI had created a table relationship in my model that I hadn't asked for and it was base on an ID which had indeed one null value. So I can fix it by either removing my relationship in the model or by removing the null values in an additionnal Power Query step.

So my function to remove accents is OK.

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June 2025 Power BI Update Carousel

Power BI Monthly Update - June 2025

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

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.

Top Solution Authors