RE:
If the feature key “Saved views support for workspaces” is activated. Then you cannot publish a workspace where a new tile already is added. If you try D365FO will then report the error message: ”You cannot publish this view as some user-added elements in the workspace are not backed by published views. Check the Action center for more details.”
RE:
Does the new functionality in 10.0.39 address your request?
RE:
There are more issues / limitations related to decimal attributes... Consider the case where a decimal attribute is activated for "reuse in configurations" and the model is used "stand-alone" (attribute values entered by the user) as well as a subcomponent in another model (attribute values calculated in and passed by the parent model). We've noticed that the "reuse" fails even if the attribute value is "the same" in the 2 configuration cases. When using the attribute in the nomenclature, it appears that the attribute has 2 decimals when entered by the user (e.g. 12.00) and no decimals when calculated and passed from the parent model (12) which is weird because after all it is a numeric in both cases...We currently use a workaround with an additional INT attribute for "reuse in configurations", but it needlessly complicates the model... would be nice if the configurator would consistently use the same number of decimals (from the UOM) everywhere and apply rounding when needed
RE:
Yes please! I thought this was a bug. Means I can't use the new slicer :( Our users are very accustomed to multi select with "Ctrl" - it is not a confusing feature at all. Please bring it back!
RE:
This functionality would be very helpful
RE:
We need to be able to have one only report with the invoice and QR code!
RE:
I can't understand why anyone at Microsoft thinks this makes sense. I don't see any possibility that we will be able to use the new planning optimization until this is fixed.
RE:
I also had this issue,I am currently working to enable Change Data Feed (CDF) on a Delta table that is sourced from a mirrored Azure SQL database. However, I have encountered an issue when trying to perform this operation within a notebook. The error message, OperationNotAllowedOnTheShortcutPath, indicates that there are restrictions on enabling Change Data Feed for a database that has been shortcutted into a lakehouse.Given this restriction, it appears that the only viable solution is to enable Change Data Feed through the SQL endpoint in the warehouse. However, the SET TBLPROPERTIES command is not supported in the SQL endpoint, which presents a challenge.