on
RE:
https://docs.snowflake.com/en/release-notes/bcr-bundles/2024_08/bcr-1784
RE:
Snowflake will oblige SERVICE user to connect without using the Username & Password, therefore potentially using private/ public key. At the moment we cannot use key pair authentication to connect power bi to snowflake. Snowflake will disable LEGACY_SERVICE user as of November 2025
RE:
I too need the format dd/mm/yyyy. The report I provide for my Power BI user base (~500 people) are mostly non-US colleagues. To anyone but our US and the handful of Canadian colleagues, the mm/dd/yyyy only creates a hurdle in data consumption.Please add the format.
RE:
This is a requirement for our business. Having dates in dd/mm/yyyy format in Power BI Service, and then in mm/dd/yyyy for data received via email subscription, is too confusing for the end user and will result in errors being made. Until dd/mm/yyyy is an option, our business cannot use email subscriptions as the risk (e.g. misrepresenting data to a customer) outweighs the benefits (i.e. having data pushed to inboxes on a schedule).
RE:
Either this or make the legends as a separate part of the page so they can be moved/sized to somewhere I have white space.
RE:
I was unable to update the comment above, but here are some thoughts. Solution considerations:Create a parameter to activate change management for direct delivery POs and a separate parameter for intercompany POsProcurement and sourcing > Setup > Procurement and sourcing parameters > Default values and parameters FastTab > Change management for purchase orders grouping > "Activate PO workflow for direct delivery POs"Re-visit the change management logic that currently resides on a vendor record. Ex: I may use a vendor for both direct delivery AND inventory POs, the current logic requires me to bypass PO workflow if I want to use that vendor for direct deliveries. However, if I use that same vendor for a regular PO, that setting will allow the regular PO to bypass workflow. It shouldn't be an all or nothing setting. Regular POs should still go through workflow for that vendor.Procurement and sourcing > Vendors > All vendors > Purchase order defaults FastTab > Change management for Purchase Orders > Allow override of settings per purchase orderNew logic is required here to potentially activate or deactivate for direct delivery orders. This new logic can override the Procurement parameters for the vendor. There's opportunity for improvement, but note that it's common for a client to require approval on ALL types of POs (Direct delivery, standard PO, planned PO, etc..)
RE:
This is such an important idea - please fix it as soon as possible! It is extremely annoying not being able to conditionally format e.g. legend series through a simple fx formula; or automatically set a slicer to a default value from a measure (or fx field).Also upvote the idea that was posted in this thread as well. I could also see values in being able to specify certain bookmarks through fx functions.
RE:
A third option should be added - let users select whether credit management should be checked against the main customer account, or the invoice account, or both. "Both" because when we are releasing an order for dispatch, we need to knowIs the invoice / Head Office account paying its bills on time?Does the Head Office need to authorise this franchisee's order before we can release it?Thanks for your consideration!
RE:
This could be a good alternative to the issue I ran into recently - the inability to apply a filter directly to a button. As long as it would work with images formatted to the visual as well!
RE:
Clients continue to have this functional requirement. All POs (including direct delivery) need to go through workflow. Is this on a short-term roadmap?