andrew_matheny
4 years agoNew Member
Status:
New
Load Errors Should Indicate Which Field/Value Causes Error
Loading one of my queries fails, the Load window simply displays a message that says: "OLE DB or ODBC error: [DataFormat.Error] We couldn't convert to Number.." The error message should display the field or value that can't be converted to a number. Otherwise this error message isn't helpful at all The typical advice of checking the data in the Query Editor preview is not helpful either when working with large datasets, many queries, or queries with many steps since the error may not appear in the preview.
2 Comments
- fbcideas_migusrNew Member
Should apply to errors reported on gateways too - no use without column info.
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
Shell/Console/Terminal for Fabric CLI, etc. in Fabric Portal
Regularly, when I start working for a client, I'm unable to use Fabric CLI due to device compliance issues. I don't want my consulting laptop to join their domain. I just want to be able to use Fab...PeterDaniels4 hours agoAdvocate IIINew3Views0likes0CommentsFile level commit - Need the ability to edit the commit description
I tried the recently announce file level commit for Fabric items. One notable issue I have with the feature (testing this with a Fabric warehouse, I'm assuming this would hold true for other items): ...DataBard16 hours agoMost Valuable ProfessionalNew36Views0likes3CommentsAdd the known commit ID by the "updates" subtab
Often I have a git commit that I want to sync into a fabric workspace, today I never know if the browser tab has actually picked up the latest commit or if it is going to throw an error on conflicts-...T-Rez16 hours agoAdvocate INew10Views0likes1Comment