Skip to main content

Vote (0) Share
's profile image

on

Comments (0)
's profile image Profile Picture

mohammad shakeri on 19 Nov 2024 06:11:46

RE:

We are still waiting....

's profile image Profile Picture

Scott Lu on 19 Nov 2024 00:39:22

RE:

either have dynamic connection like Lakehouse & Warehouse or have parameter settings.ATM.devops is a fake process, we have to change Fabric Pipeline for source connection, I find a way to make destination (Lakehouse or Warehouse) dynamic, but we couldn't work out for source connection (if source is not lake house and warehouse)

's profile image Profile Picture

Hari Pendyal on 18 Nov 2024 22:59:57

RE:

fix it

's profile image Profile Picture

Pär Adeen on 18 Nov 2024 22:55:28

RE:

Tried to implement this with highlighting but that’s impossible to do generic. So please implement this in the visual domains

's profile image Profile Picture

Alireza Eshaghzadeh on 18 Nov 2024 22:11:37

RE:

I have submitted the following idea, providing a detailed overview of the fields that should be added to the Electronic Reporting (ER) Jobs form. The requested enhancements aim to improve usability, enabling more efficient filtering, searching, and management of specific documents within D365FO:https://experience.dynamics.com/ideas/idea/?ideaid=807dad85-f9a5-ef11-95f5-0022485288a6

's profile image Profile Picture

Sue Driscoll on 18 Nov 2024 21:47:42

RE:

Especially useful to record photos of damaged goods on receipt.

's profile image Profile Picture

Daniel Coelho on 18 Nov 2024 21:38:43

RE:

This is currently supported in the latest Fabric Spark Runtimes (1.2 and 1.3).

's profile image Profile Picture

Sam F on 18 Nov 2024 21:07:32

RE:

Truly baffling that this wasn't implemented immediately as part of the grouping capability, no less that it still hasn't been so many years later... it's one of the single most basic, foundational features that any user would need when adding custom groups. The workaround of creating a separate mapping table and adding a calculated field value for every single record in the dataset is one of the most egregious examples of adding unnecessary complexity and creating redundant data for such a basic and simple exercise that I've ever encountered. Excel pivot tables have been able to do this for at least a decade, if not longer (not to mention in a much more convenient way by clicking & dragging fields right on the table/visual itself, another area on the list of features in which PowerBI is many years behind Excel in... but I suppose that's beside the point for this particular issue).

's profile image Profile Picture

Michael Brodie on 18 Nov 2024 21:02:49

RE:

+1 This would be handy to have more control.

's profile image Profile Picture

Marco Cruz on 18 Nov 2024 17:03:28

RE:

Thanks for publishing this idea, it would be very useful to have this. I would avoid workarounds and simplify the monitoring process of our PBI applications.