on
RE:
When I do something as simple as clicking the little eyeball icon next to a field in a semantic model layout, it CHANGES THE ZOOM LEVEL ON ME.
RE:
This needs to be higher up. My organization uses Databricks as its system of reference and this would be an ideal solution. Unfortunately, because of our private network and firewall setup, we aren't even able to test this.
RE:
To enhance debugging and efficiently identify reports users reference, we propose implementing the following DAX measures:Report Name in Footer – This measure will dynamically display the report title in the footer. When users report issues and share screenshots, the exact report can be identified, allowing developers to quickly locate and resolve any concerns.Semantic Model Information – This measure will retrieve the semantic model linked to the report. Understanding which dataset powers the report helps in diagnosing data-related issues and ensuring the correct model is being used.Workspace Information – This measure will capture and display the workspace in which the report is being accessed. This is crucial for identifying the environment, permissions, and versioning differences that may affect report behavior.Implementing these measures will streamline troubleshooting and improve user support by providing essential report details upfront.
RE:
This will be useful for pipelines that runs on schedule.
RE:
100% needed. The current font library is severely lacking and inhibits users from developing themes aligned to corporate branding standards.
RE:
Useful feature, would be great to be implemented on every visuals.
RE:
The Subscription Billing-Revenue Allocation should support combining Non-Revenue Allocation SOs and Revenue Allocation SOs into a single invoice. Currently, this results in an error, preventing proper invoicing. Please address this issue to ensure seamless billing.
RE:
I also have to deal with this problem, it should be fixed ASAP.
RE:
This feature would be highly appreciated. In standard functionality there is no way of handling the returen process of a sold item in conjunction with repairs that need to be done. Customer sends in broken item, item is repaired by service technician and sent back to customer. Standard can either handle the return of an item and create a credit memo or a new sales order by using the return orders, OR it can handle servicing an broken item in a service order, but this without covering the physical return of this item / the warehouse processes (inbound/outbound). This requested feature would solve this problem: Reurn Orders would take care of the inbound warehouse stuff, the Service Orders the outbound related postings/documents.
RE:
Please help to fix this.