on
RE:
And when we update our Business Central say we have 14 customs projects to publish after update that are all on version 1.0.0.0 sometimes the update unpublish all our extensions then we cant publish the same 1.0.0.0 version its saying you already installed before this version ( and its not even published or installed right now ! ) So you have to increase version in 14 different projects build them again and publish ! Thats Crazy..
RE:
This isn’t just an idea — it’s something Microsoft should have implemented already!!!
RE:
Inline images listed as attachments is very confusing in the crm timeline, @microsoft, can you address this? Thanks
RE:
Good idea!
RE:
Fully agree — inventory aging should not reset when items are moved between warehouses. Using the original receipt date from the PO ensures accurate aging and better stock management.
RE:
Table stakes feature. Huge miss that this basic functionality isn't existing.
RE:
You could use the Business Central API for a supported way to extract data. When you connect with dataflow it is actually the API behind the scenes. You could do the same data extraction but better using python in Fabric or else where.regards Jonas Hertzjonas.hertz@bispecialist.se
RE:
This is extremely important for customers would like to utilize this great Physical Inventory Orders feature but they are using Expiration Dates. At the moment, Physical Inventory Orders are totally unusable for these customers...
RE:
I think this is not related to CI-D but to general Dataverse as no edits nor bulk edits are done in CI-D.
RE:
The restricted regions feature is required for compliance within our distribution workflow. This is essential to ensure the correct product is shipped to the correct region and countries do not receive products that are not regulated for use in that country.