RE:
This doesn't seem to have been fixed. It's still using the description of the G/L Account instead of the description of the recurring purchase lines.
RE:
In huge need of this feature!
RE:
This would be a great add!
RE:
Voted this up for the custom Case ID. Being able to include a date (non-onprem) would be ideal.
RE:
Here's hoping this feature gets added. There are workarounds (e.g., creating grid shapes that you use to align), but it is a pain to maintain or change. Can't tell you how much time I waste trying to align objects in Power BI simply because we can't alter the grid size. Having this feature would go a long way in making it easier to maintain/standardize report designs at scale for numerous reports in an org.
RE:
I'd suggest looking into Activators to stream pipeline failures to alerts. You can get pretty granular with rules, and it supports both emails and teams messages as actions. I think these are relatively new, so might not have been available at the time this was submitted.Here's the MS link for the documentation:https://learn.microsoft.com/en-us/fabric/real-time-intelligence/data-activator/activator-introductionThe activators will give you direct access to things like the workspace name, with nothing more than a click. But, just so you are aware, it is also possible to use sempy.fabric to programmatically identify workspace names and objects. You shouldn't store a static list which would need to be maintained.https://learn.microsoft.com/en-us/python/api/semantic-link-sempy/sempy.fabric?view=semantic-link-python
RE:
It would be very usefull to be able to export matrices to excel and have the same formatting there. Is there any solution? Will it be possible? Is there an add in for it?
RE:
This should have been done long ago!
RE:
I believe current functionality also goes against MS best practices, but there is no way for a user to opt-out of the current functionality. Best practices: https://learn.microsoft.com/en-us/azure/databricks/lakehouse-architecture/reliability/best-practices