on
RE:
https://learn.microsoft.com/en-us/fabric/release-plan/data-engineeringhttps://learn.microsoft.com/en-us/fabric/release-plan/data-warehousehttps://learn.microsoft.com/en-us/fabric/release-plan/data-factoryCan someone tell me which one of these roadmaps states that this is being worked on, because I do not see any evidence of it. And what blog has these updates?
RE:
The External Catalog / Punchout functionality offers excellent efficiencies. However, without being able to handle freight charges via Charges codes (or other options) the functionality is severely limited. We will not be able to use this for some of our largest vendors.
RE:
I support this idea. Actually I think it could be even more granular than Persona. I think we should be able to even select specific Item types.
RE:
Please provide a more recent update on this. It's been six months and this is a very highly requested feature. Let's now force customers to use 3rd party tools for something basic like this that even Excel can do.
RE:
This would be really useful; I could do with this functionality most days.
RE:
Effective Representation of Large Hierarchical Data: Treemaps provide an excellent visual tool for exploring complex hierarchical data structures with numerous categories and subcategories. Their nested rectangle structure enables viewers to grasp the relative sizes and relationships between various data points at a glance.
RE:
Why is this marked as completed? Power BI Desktop does not have true Git integration. It still needs a proper Version Control pane just like VS Code, with the ability to clone, pull, branch, commit, push, create PR, etc.
RE:
This idea needs more focus. We are using more and more dataflows and have no way of checking them.
RE:
For GL account reconciliation, it is very beneficial to have the Purchase or Sales invoice line descriptions carried over to the G/L Entry for all line types. Many other ERP systems have this feature built-in.
RE:
The number of allowed scheduled refresh failures should be configurable on Capacity level.The scheduled refresh time-out is currently set to five hours (and we cannot change it) on Premium capacity. The capacity can be easily overconsumed by one semantic model when it is repeatedly trying to refresh three times in a row for five hours.