on
RE:
Yes, I absolutely agree with the topic. If the assembly is calculated using the "Calc. Production Std. Cost" function, the value does not correspond to a produced assembly because the non-inventory items are missing.I don't know whether that's correct from a financial perspective.What is also interesting is that the cost price of the non-inventory items is not updated correctly due to purchases. This is always on FiFo, but the regulation does not apply here. The preliminary calculations using the “Calc. Production Std. Cost” function are therefore incorrect.
RE:
Great idea. This is critical for a business like ours where a Tag represents one unit for sale. Ie when we produce more than planned, like 11t instead of 10t we need to reserve and sell the full quantity. We can't reserve partial qty of a coil.
RE:
Please fix it in desktop Excel. It has been broken way too long!
RE:
Hi, I think that a such feature it could be very useful ... let's think to a Spark notebook.
RE:
Hi, a such feature it could be more important for some my customers.
RE:
This will represent a significant improvement in the UI.
RE:
We need this
RE:
same idea here: https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=d24a6f04-eb65-ed11-a76e-281878a5e183
RE:
+1 1) to make more compatible SQL surface area with SQL Server or Azure SQL Databases, especialy in migration scenearios 2) I know about spatial functions in Python or KQL, but if your architecture is focusing to relational DWH, is big pain to solve spatial needs (spatial datatypes, and simple spatial functions like distances, area, or intersects) outside DW,
RE:
Additional two similar ideas:https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=470628aa-8f44-ef11-b4ac-6045bdbb350dhttps://ideas.fabric.microsoft.com/ideas/idea/?ideaid=6d72e835-ba33-ef11-a295-6045bdb16ed2