RE:
Feels fundamental. The amount of time PBI developers must waste trying to work around simple stuff like this is incredible. Also being able to filter correctly when userelationship filters are used (and ensure the conditional formatting works as well, currently only conditional formatting works for records that go through the primary relationship)
RE:
@ Sakshi Jain (administrator) - Echoing the previous poster, what is the expected timeframe for this? It is currently affecting customers and I would like to have something to report back to them on.
RE:
Hi there,Could you please merge with this idea:https://community.fabric.microsoft.com/t5/Issues/GetAppUsersAsAdmin-API-Audience-Support/idi-p/2833610/page/2#commentsThanks,Pedro
RE:
Hello, I also highly recommend this idea to take into consideration and implementation.With ISV solutions, I know (Inway, Sycor, Arineo...) you are able to create a journal behind the statement, check / validate the processed matching rules and correct, if something was matched wrong, before posting the journal / statement lines for years.Reversal and correction within Modern Bank Reconciliation is much more complex and user unfriendly, from European point of view, how we handle Bank Statement Postings.
RE:
Still under review from 2022, it's badly needed!
RE:
Any update on this?
RE:
It is a must have, cannot believe this is not already available. Having to re-create the drill down pages so they are sorted by the created order is painful. Currently I duplicate all the drill down pages in the order required, delete the original page then rename the duplicated page to the original. A horrible and painful process particularly when you have many pages - the page scroll at the bottom of the editor to go back and fourth when duplicating and renaming pages is such a waste of time to achieve something that should be so simple. Love the product but this bit is very annoying.
RE:
Comparison word clouds are often much more helpful… showing only the words that are different between 2 items.
RE:
A very necessary feature. Can you explain the workaround you've found though?
RE:
so sad this doesn't seem to be available 5 years later!!!