on
RE:
please help us! we need to be able to import materialized views
RE:
This is essential! On my laptop no matter what I do I cannot hover to get certain icons to show. I have to wait until I can hook up to a big monitor. And sometimes it's difficult to get the icons to show up even on that! It's extremely frustrating.
RE:
This should be a no-brainer to implement.
RE:
This is definitely a must-have for any business hosting webinars!
RE:
It exist with Webinars created from Teams, but like too many other options, they should also be available in Webinars organised within Customer Insights
RE:
Looks like BC25 will have "this" keyword.
RE:
I should have added that it would also be more user friendly if you could multi-select several lines in the list of snapshots and then click "run snapshot once" so you get the latest set of balances for several companies at once.
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