on
RE:
Yes, please is needed for companies with multible legal entities.
RE:
This still seems to be an issue as of May 2024.This "feature" is hinted at in MS documentation but that relates specifically to the display of Int64 values in Power BI visuals. I believe it also affects some Power Query Table.Join and Table.NestedJoin operations - at least where these are not folded back to source databases.I suspect this stems from that fact that Int64.Type is still basically type number in Power Query, just with facets that indicate that it is semantically an integer. Since type number has to support floating point, and the internal implementation is presumably an IEEE double precision floating point number, we end up with only 53 bits of usable integer precision. (Maybe the Power Query library type ought to have been named Int53).As for resolution - To avoid breaking existing code, maybe the internal calculations should use IEEE quadruple precision instead of double precision. However, I agree with the original poster from 2016 that this is particularly an issue with IDs used for relationships. In this application, the numeric significance of the value is less important than its uniqueness and ability to be compared for equality. Maybe a PQ library type based on binary type with facets, rather than number type, would be more useful? (It would probably also be useful to add e.g. some hashing functions to the library to return values of this type.)
RE:
This is the way it works in task scheduler in windows server.It should be the same for PBI.I have also the problem with needing different refresh times on different days.
RE:
Totally agree! First item chosen and added to products basket should show as first line on the quote - and so onwards. This is a huge problem for our sales teams as our quotations require a specific order of presenting the products to our customers. Having to correct this sorting order manually in the quote by changing line numbers -no drag & drop function :-( - is very inefficient, time consuming and leaves much room for error.I cannot really understand why there isn't much more voting/comments around this topic?After all, in almost every online ordering tool I know chosen items follow this routine of first item on first order line, etc.
RE:
This feature would help us convincing customer to transition over to Microsoft Fabric
RE:
Agreed - this would be very useful for companies looking to implement a LH-LH-DWH medallion architecture, writing from Silver LH to Gold DWH. Also this limitation damages the overarching narrative around OneLake: to have flexibility behind reading and writing data between the different engines.
RE:
Agreed - this would be very useful for companies looking to implement a LH-LH-DWH medallion architecture, writing from Silver LH to Gold DWH. Also this limitation damages the overarching narrative around OneLake: to have flexibility behind reading and writing data between the different engines.
RE:
Users accustomed to Excel's Pivot tables have expressed similar opinions. I think the matrix will be easier to read once this is implemented.
RE:
It's a thoughtful observation to recognize the impact of the current database log setup on auditing capabilities. Your suggestion for Microsoft to consider a revision of the logic behind the database log is constructive and highlights a potential area for enhancement. It's positive to see proactive engagement in seeking improvements that could benefit the auditing process. Looking forward to seeing how this idea progresses and the innovative solutions that may emerge. Thank you for sharing your insights!
RE:
This feature is definitely necessary because when you are presenting dashboard to people you need to explain people what those matric for. If just making buttons alongside with table graph you either make tooltip button outside of graph and cost space or you make them near headers but get messed up if the table can scroll horizontally.