Forum Discussion
'OLE DB or ODBC error: [Expression.Error] The value "" cannot be converted to the Table..'
- 4 years ago
Hi, v-yalanwu-msft
I solved in another way that I post here in the hope that it will be of help to someone.
First, I started to expand from the beginning of the query the columns and locate which column was causing the issue.
Second, i removed the passage where I expand the problematic column and i added a custom column which has this function:
Table.AddColumn(#"Problematic Column", "NameNewColumn", each if [#"ProblematicColumn"] is table then "[Table]" else if [#"ProblematicColumn"] is record then "[Record]" else if [#"ProblematicColumn"] is list then "[List]" else if [#"ProblematicColumn"] is function then "[Function]" else [#"ProblematicColumn"])
Third, i used filter in the "NameNewColum" trying to locate if there was any other values besides [Tabel] and I actually found that there was some rows without any kind of values (note that the column quality tools always reported 100% valid values). I proceeded to filter only the table values then.
Fourth, i proceeded to expand the problematic column with the filter applied and then the error does not show up anymore.
Hopefully this will be helpful for someone in the future,
Manuel
Hi, v-yalanwu-msft
I solved in another way that I post here in the hope that it will be of help to someone.
First, I started to expand from the beginning of the query the columns and locate which column was causing the issue.
Second, i removed the passage where I expand the problematic column and i added a custom column which has this function:
Table.AddColumn(#"Problematic Column", "NameNewColumn", each if [#"ProblematicColumn"] is table then "[Table]" else if [#"ProblematicColumn"] is record then "[Record]" else if [#"ProblematicColumn"] is list then "[List]" else if [#"ProblematicColumn"] is function then "[Function]" else [#"ProblematicColumn"])
Third, i used filter in the "NameNewColum" trying to locate if there was any other values besides [Tabel] and I actually found that there was some rows without any kind of values (note that the column quality tools always reported 100% valid values). I proceeded to filter only the table values then.
Fourth, i proceeded to expand the problematic column with the filter applied and then the error does not show up anymore.
Hopefully this will be helpful for someone in the future,
Manuel