on
RE:
Filter strings used to be limited to 250 characters, but I'm pretty sure that limit was extended considerably, so you could even go to 2048 characters
RE:
I'd suggest allowing filter sets of 1024 chars to increase capacity of the functionality, and then trimming the pipe if the string needs truncating should the user for some reason exceed that capacity.
RE:
When can we see the ability for Power Automate visuals to work in an embedded app/report?
RE:
Is there anything news regarding getting FIK-75 implemented into Business Central ?
RE:
Need conditional formating in Card Visuals for showing KPI.
RE:
Need conditional formating for showing KPI.
RE:
This is needed. It is mandatory to view the uploaded invoice from any documents. Lets us say if we uploaded the order in sales order then we should see that sales order document too in f & o from any other screens also like posted invoice, packing slips etc.
RE:
An option to freeze columns in the matrix has been added, which is a great feature. However, there is room for further flexibility.Currently, this functionality is designed for scrolling through measures. When there are many categories that don’t fit into the table without scrolling, the scroll bar disappears.To enhance usability, it would be beneficial to introduce full flexibility. For example, the ability to freeze specific categories, select exactly which ones to freeze instead of all the rows, and ensure the scroll bar remains available in all scenarios, similar to Excel.Link to the discussion about the issue from community:https://community.fabric.microsoft.com/t5/Desktop/Freeze-columns-in-Power-BI-tables-or-matrix/m-p/4365598#M1363193Thank you, Rita
RE:
Are you aware of the REST api? ("queries" endpoint)? Can you use that on databricks? Can you explain second sentence? Python libraries are commonly implemented as "wrappers" around other runtimes (like jvm, rust, native, and so on). The way that sempy places a dependency on a .Net is not any more unusual than the design of pyspark itself. In any case, the .Net dependency probably originates back to an earlier variation of the library (called "pyadomd").
RE:
The feature is marked as planned for Release Wave 1 2025, however, I am not seeing this listed in the release planner for Wave 1 2025. This is a huge feature that we need to have in CIJ especially as more clients are migrating from the likes of Pardot and Marketo where this is standard functionality for forms. Do we have an ETA as to when this is going to happen? Would love not to have to create JavaScript for these types of requirements. Thanks!