on
RE:
Hello Gerardo,We happen to have this feature in our addon that we developed.You can attach and view your documents not only in your projects and project planning lines, but also in many other Business Central pages.If you or anyone else is interested in the Attachment Viewer, visit our AppSource offer and contact us for more details.Kind regards,Barbora GolasowskaOn Point Ltd.
RE:
Hello Morten Andreasen,We happen to have this feature in our addon that we developed.You can attach and view your documents not only in your projects and project planning lines, but also in many other Business Central pages.If you or anyone else is interested in the Attachment Viewer, visit our AppSource offer and contact us for more details.Kind regards,Barbora GolasowskaOn Point Ltd.
RE:
We are still waiting....
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)
RE:
fix it
RE:
Tried to implement this with highlighting but that’s impossible to do generic. So please implement this in the visual domains
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
RE:
Especially useful to record photos of damaged goods on receipt.
RE:
This is currently supported in the latest Fabric Spark Runtimes (1.2 and 1.3).
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).