on
RE:
This functionality is crucial as it allows for the ownership of a created lakehouse to be changed through a UI/REST API. Our organization has a strict policy that production objects should not be owned by individual user accounts. Please kindly provide a timeline on when this would be available.
RE:
This seems to be the default behaviour in Power BI. Even where rows differ, if you only add columns where they are the same, you get just the unique rows. The way round this is to add some kind of key column, which forces all rows to be displayed. The simplest way to do this is add an index column in Power Query. This is of course not ideal, using canvas space to show an unneeded field just to force a behaviour. I mentioned this in the Visual Calcs feedback thread. That update introduces the concept of hidden columns. Unfortunately, it did not allow it for all scenarios, though it would be useful in cases outside the scope of visual calcs. I can't say that development is planned, but do know this scenario has at least been seen by a product manager.We have a similar case - for audit, rows must always be displayed separately. Currently, a compound key is displayed in the column to ensure this is the case. This is also needed to provide the hook for drill-through pages. This would in our case be fixed by allowing columns to be hidden without alteration of the underlying table. Other people may find they do not have a key field and would like an option to force rows to never combine.
RE:
Can you please post this item in the new backlog or planned list, when can we expect this. Is really confusing for the users. Thanks!
RE:
The hierarchy view is one of themost used features in all customer projects I know, it is imperative to keep the functionality, or modernize it, if required by the new user interface.
RE:
The majority of our customers use this function. It is an important tool not only for accounts but also for product groups to get a quick overview of the hierarchy. It is not an option for our customers to lose this feature.
RE:
I also got same issue. No solution yet.
RE:
Client certificates come for free with a properly implemented TLS stack. Lack of support for client certs looks like a bug rather than a missing feature.
RE:
Looking for details on how to integrate Excel with a client-certificate/smartcard protected data source. The docs are silent on TLS.
RE:
Totally agree with Terri B...the formatting options to set column widths in tables and matrix is a real problem.