I hit this error almost everytime I try to automate a datadump and one of the fields may have a different data type than expected.
Need to automatically detect data types, but also help user pinpoint which column is throwing the error and is mismatched.
I have sheets with many columns and it is very tedious to figure out which one is causing the issue.
Error returned: 'OLE DB or ODBC error: [Expression Error] The key didn't match any rows in the table
No CommentsBe the first to comment
Recent ideas
Support QR codes in the barcode scanner in the Power BI app
I was surprised to find that the barcode scanner inside of a Power BI report in the mobile app only supports scanning barcodes, not QR codes. Our warehouse uses QR codes everywhere, so I cannot use t...Jaap_O_RFH2 hours agoNew MemberNew13Views0likes0CommentsAllow enabling Lakehouse Schemas on an existing Lakehouse
Right now Lakehouse Schemas can only be turned on when you first create a Lakehouse. If you already have one running in production and later decide you need schemas, there is no way to enabled them o...AlessioAndriulo3 hours agoAdvocate INew8Views0likes0CommentsAllow enabling Lakehouse Schemas on an existing Lakehouse, without recreating it
Today, Lakehouse Schemas can only be turned on when a Lakehouse is first created. There is no supported way to enable schema support on a Lakehouse that already exists — the only workaround is creati...AlessioAndriulo3 hours agoAdvocate INew28Views4likes0CommentsWorkspace Folder & Subfolder Inventory View for Power BI Reports and Apps
Problem: Many organisations use Power BI workspace folders and nested subfolders to organise reports by department, business area, project, or function. While this structure helps keep content organ...rijesh3 hours agoFrequent VisitorNew8Views1like0Comments