Workspaces are simply tile based forms to show related information in one place in standard organized pattern.
Most of the standard menu items are removed from respective modules and placed directly under workspace tiles. Like example in previous version of Dynamics AX the menu item for units was different now in D365FO its only under Product maintenance tile.
The basic idea is the similar feature of cues from Dynamics AX but with enhancements. It contains some buttons for action or to show some filtered grid (under workspace tile pane), list of data in modern grid format (tabbed list container), fancy charts (workspace chart pane) and related links (related links panel).
The module procurement and sourcing for purchase orders activity have many stages, just by looking as purchase list page which show all purchase orders with various statuses and action required to turn this junk complex information into smaller with limited features with some nice graphs for analysis sufficient for end user instead of clicking and navigating to many places which could be frustrating and time consuming. All this info at one place is a workspace. The standard name for this workpace is Purchase Order Preperation
Workspace can be create in many ways the 2 know ways are:
Visual studio is required and can be developed on dev environments only which means no direct creation on live.
Directly on any environment without visual studio, the trick is creating a tile linked to power apps like power BI
Microsoft has added new certifications in line for Dynamics 365 F & O which now covers more functional areas with reasonable meaning. Before this was not the case only few certifications were/still available for AX 2012 versions compared to massive modules available.
MB-300 Microsoft Dynamics 365 Unified Operations Core
This certification covers intro to most of the best features related to functionality, LCS, security, data migration and support
For more please follow this page and donate to support.
First understand variations, the item having multiple variations created using product masters. Example: Item pen maintains a one item code with different variations like color: blue, red, green and black. Otherwise create new item code as blue pen, red pen, green pen and black pen. Item variations are used in dimension based configurations.
While creating a new item code select
Product sub-type: Product master
Configuration technology: mostly it is predefined variant change it to dimension based configuration
This is only used when creating routes and to maintain versions by defining rules which item during production order or sales order picks and unpicks item automatically.
Example: The Sales order of phones having multiple accessories included based on warehouse location then no. of accessories to be included or removed automatically during the process is based on configuration rules for bom items.
BOM version: Allows to change BOM overtime, example: swapping items, configurations or removing components if not applicable
Graphical BOM: Design a BOM graphically
Sub-BOM: Control the BOM type that can be sold, revised or planned independently. If BOM contains another BOM as component then this is multi level BOM. Sub BOM is refered as level 1 and its components as level 2
Sub Contracting: BOM component is supplied by a contractor or a purchase order BOM list shipped to the supplier, additional BOM line that contains the service is included to book the cost of sub-contracting. Note: When BOM line is sub BOM then additional production orders are created
Quantity dependent BOMS: control which version of the BOM is used in Productions based on quantity in production order
Site dependent BOM and routes
Phantom BOMS: same like regular BOM however components can be re-used. Example: One BOM for Concrete which can re-used for each and every new BOM for concrete moulds
BOM calculations for manufacturing a particular BOM