on
RE:
It is important to have this functionality because this at worst case creates performance issues.
RE:
Great idea!
RE:
Great idea, I support and hope we can do it together
RE:
Great idea. O
RE:
Discouraging to see over 400 votes, over 6 years, and still no movement. Is any development being done?
RE:
Hi @Beatriz Nebot Gracia Thanks for suggesting to log it as a bug, we did so and @Microsoft support team responded as following:QUOTE:This is a known issue and has been mentioned on deliverable # 964201 : If a unit of measurement is deleted, the planning optimization is still triggering a warning message that this unit is missing for the items it was previously used for.The fix will be released on version 10.0.42/Platform Update66 as our PG mentioned.UNQUOTE:
RE:
Very great idea!
RE:
Much needed feature. Please provide some default options to display True/False boolean values as Yes/No, Y/N, On/Off, Open/Closed, Enabled/Disabled, etc. Even better to allow custom format strings (just like what the date/time data type already supports).There are not many votes here, not because this feature is not needed, but because the customers currently can get by with a calculated column translating True/False to Yes/No or whatever they need. But that inflates the data model and results in an ugly solution.On top of this idea, how about add another Power BI function "Display as"? Just like Power BI allows you to sort one column by another column, maybe allow to display the values of a column based on another lookup table manually entered in Power Query as part of the data model? I think that will be a generic solution to many problems currently faced by many silent customers!
RE:
I agree and have several customers now that are considering using an ISV for managing their trade allowance agreements because we cannot fulfill this requirement. Thanks, Traci, for submitting this idea.
RE:
My vote for this idea, this could be really useful. For example, a simple task like finding the first/last sales date for an SKU sometimes requires hundreds of thousands of database queries, since we have to query each combination of item/variant/location separately. SELECT MIN([[Posting Date]) with GROUP BY would be much more efficient.