The SysExtension framework in Dynamics 365 for Supply Chain Management often fails to recognize newly created classes due to intensive caching of class IDs and attributes. This issue persists even after rebuilding the solution and performing an IISRESET. The solution is to clear the SysExtension factory cache by executing a
Today, I revisit a project of my youth: the Petty Cash addon for D365FO. Born in 2002 and finally released globally in version 10.0.40, its utility seems limited in Western Europe, where separate bank accounts suffice. However, in Eastern Europe and industries like construction, it still holds relevance.
The Dynamics 365 Warehouse Management app utilizes a container-based system for control layout, incorporating heuristics and customizable rules. Controls without default values prompt user input in the Primary Input Area, creating a seamless experience. Strategic management of controls and rule customization ensures efficient workflow and user-friendly interaction within the app.
When utilizing configurable business documents (Electronic Reporting) in Dynamics 365, additional steps are required to dispatch various documents such as invoices, delivery notes (referred to as packing slips in the US), sales order confirmations to customers, or purchase order requests to suppliers. Begin as usual with Accounts receivable > Setup >
One – if not the – notorious error in Dynamics 365 related to production and warehouse management manifests itself at the “Production floor execution” terminal during reporting as finished (RaF). On the screen, the error message “An error occurred while processing the job…” is displayed. In the activity center, you receive
Low value parts such as bolts, screws, gaskets, clamps, and other fasteners, as well as small electric parts, are rarely retrieved from the main warehouse in the precise quantities by production order. Instead, they are stored in surplus at the workbenches, typically organized in boxes of various sizes. The usage of
