damansinghNew Member9 years agoStatus: NewDataFormat.Error: We couldn't convert to NumberDataFormat.Error: We couldn't convert to Number. Details: 2014219586-S
Recent ideasAll Idea StatusesNewNeed ClarificationNeeds VotesUnder ReviewPlannedCompletedAbandonedTagged:TagMost RecentAccessibility issue in the Share dialog of embedded Power BI reports Accessibility issue in the Share dialog of embedded Power BI reports I would like to share an accessibility finding identified while testing an embedded Power BI report published as part of the cont...Lakehouse identity column It would be nice to have support for identity column in DDL for lakehouse Data Lineage support for Notebooks I would like to be able to utilise and benefit from the Data Catalog Data Lineage, even when I am not utilising the required Pipeline Activities that generate Data Lineage metadata. I think this sho...Display Table[Column] instead of Column Name in Conditional Formatting Dialogs In large-scale Power BI semantic models, it is common to have identical column names across multiple fact and dimension tables. Examples include columns such as Status, Category, Region, Employee ID,...Native SAP SuccessFactors and Active Directory Connectivity for Simplified Data Integration Having native connectors for SAP SuccessFactors and Active Directory would eliminate the need for workarounds such as notebooks, custom scripts, or complex integration setups. Users should be able...
