Microsoft Dynamics 365
This is a clear problem of non-existent functionality. However, in the current functionality, there is another problem, derived from the existence of products with different tax rates or with application of a discount for prompt payment.
This idea proposes to enable ending without a report as finished journal.
I can fully support this idea which is quite generic in as well discrete as process manufacturing industry.
Workaround suggested in the past to register a dummy report as finished, which must be scrapped in inventory does not suit the industry requirement.
By implementing this idea we will:
• reduce unneeded and fictional administrative actions which are probably performed by different roles (SOX impact)
o register report as finished on the order by an operator/planner
o scrap a quantity by the warehouse responsible
o end production order by a financial responsible
• bring the ERP process back in line with business reality, where some productions do not result in an actual yield due to a variety of possible causes:
o nature of the product (e.g. chemical/ biological circumstances) making production results uncertain
o nature of the production (e.g. trial orders)
o cancelling a production order before completion
• provide a more correct and transparent reporting, as well for production efficiency as for scrap reporting.
A very detailed information about the differences between BLOB and Media, could be seen here:
But sadly that issue was closed unsolved after about two years.
So, how long is a "long term roadmap" approximately? ;-)
Can we expect any progress in the future?
Can this please be put on the roadmap ?
This is especially useful when you set up a tablet/mobile profile.
Those are most of the time very specific, and most of the actions are obsolete for that profile.
But now we have to solve this by using page-extensions and hide the actions by code.
В утвержденных заказах на покупку, прошу предоставить доступ вложению документов (без запроса на изменение).
Add the ship to table to the config pack. Table 222
If you use the select fields functionality from the config line menu options , you are able to update only certain fields. This works today and has been like this for sometime. The field selection can get overridden and reset so it’s important to always review the package records before applying.
It is a basic report on any ERP. Hurry up and develop it on Business Central. All the customers need it.
I don't care if it supports .NET Core or not, I'd just like to know how to create a new plugin in VS 2019, now that .NET Framework isn't one of the options. At least update the docs to indicate what you should choose now. But voted, because supporting .NET Core would also solve the problem.
For purpose to easily visualize and play-compared centralized robotics recorded expectations versus actual actions.