on
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.
RE:
1) The ability to set Spark Table Properties on the underlying Delta Table that is managed by the Warehouse would potentially enable this and many other features.2) Fabric Mirroring is especially important to have this feature. Fabric is using CDC to replicate a data source into the lake - but we can't use CDC to get that data out of the mirrored database, even though its all Delta under the hood.
RE:
Please vote for this idea. I appreciate your time and effort.
RE:
This is definitely needed. We have the ability to select a particular datawarehouse as a destination of a dataflow but even if the schema name is specified as part of the new table name like schema.table, the table is only created in the dbo schema with name "schema.table" - which is not the expected. As a work around you always have to create a table manually, and then specify the destination as an existing table - which is a lot more work and not fulfilling the requirement of selecting the proper destination.
RE:
This is a complete no-brainer. The system should have FULL printing capabilities for financial statements, including formatting of headers, orientation, and footers.