ODBC connection - field already exists

[AlexMUC]

Dear Power BI community,

I just got started with Power BI and have (hopefully) only a minor issue.

I successfully connected with our ODBC database, which contains all the data from our business software. Until today we use Excel for reporting without any issues and Power BI seems to be a reasonable step forward.

I get a list with with over 400 tables when I connect to the ODBC data..the way it should be. However as soon I choose one of the table to show (and edit) the underlying data, I get the following error:

"Expression.Error: Field "UID" already exists in the database"

UID is the "unique ID" from our software and connects all the different tables, so this makes perfectly sense. However I don't need that for the reporting and would like to rename/delete that field. The problem: I don't even see the underlaying table with the error message. 

Can anybody help? I'm stuck... 😞

Many thanks in advance and best regards from Munich

Alex

[Anonymous · Accepted solution]

@AlexMUC,

Does the issue still occur when you write specific statement in the screenshot below to connect to this table?

Or you may need to rename the columns in your database to improve the readability of column names.

Regards,
Lydia Zhang

[Anonymous · Accepted solution]

@AlexMUC,

Does the issue still occur when you write specific statement in the screenshot below to connect to this table?

Or you may need to rename the columns in your database to improve the readability of column names.

Regards,
Lydia Zhang

[AlexMUC · Accepted solution]

Hi Lydia,

Many thanks for your reply. I tried a little bit back and forth in the last days and found the following:

Same thing happens in Excel with Power Query. I'm not really familiar with SQL, but figured to access the tables in my ODBC database directly with

select * from [Tablename]

and it works fine. Not sure if this is an elegant solution, but it works fine for my needs.

With best regards

Alex

[Anonymous]

@AlexMUC,

Glad to hear the issue is solved. You can accept appropriate reply as solution. This way, other community members would easily find the solution when they get same issues.

Regards,

[malatwork]

I had this too... seems like a bug... quite confusing to a new user especially since it's not intuitive there's a query behind the scenes or if it's possible to edit the query or if you have to start from scratch. The ramifications are painful to work around especially since I have 4 tables I'm joining each with long and cumbersome names I need to determine by connecting the normal way and closing out of that.

Of course all tables in my Quickbase ODBC connection are going to have Record ID as the primary key...

[AlexMUC]

Did some more research and it seems like this is a specific problem with import from 4D data via ODBC.

-> https://stackoverflow.com/questions/43221692/connecting-to-4d-database-in-power-bi-via-odbc

Any idea how to fix this?

Many thanks in advance!