Date fields on NAV 2018 sales orders can be confusing, but used correctly, they will improve your sales order processing. The dates are designed to allow you to plan the shipments to meet your customer’s delivery expectations.
Date fields on NAV 2017 purchase orders can be confusing, but used correctly, they will improve your purchase order processing. The dates are designed to allow you to schedule the receipt of product in time to meet your shipment commitments and your customer’s delivery expectations.
The order of the columns in a table in a Power BI dataset doesn’t matter all that much, especially because the Fields pane in Power BI Desktop ignores the original column order and lists the columns in a table in alphabetical order. However there are a few situations where it is important, for example when you are using the DAX Union() function in a calculated table: as the documentation states, when you use Union() “Columns are combined by position in their respective tables”. You might also find it irritating if the columns you see in the Data or Relationships panes in the main Power BI Desktop window make it hard to browse the data or create relationships.
Logging into Dynamics NAV as a Purchasing Agent, Gwen walks through the steps to process a purchase order completely. She covers everything from initial set up of the purchase order, options for posting and sending to the vendor, and where to find the purchase order after it has been posted. Gwen demonstrates a different type of set up to make the process easier to track received goods including back ordered items.
A new feature that has been overlooked in the recent blog articles highlighting what is new in Dynamics NAV 2018, is the improvement made to creating a Purchase Order (PO) instantly, from a Sales Order (SO). Although Dynamics NAV 2017 did introduce the function to create a Purchase Invoice from a Sales Order, that had an obvious limitation; a Purchase Invoice document forces you to receive and invoice simultaneously upon posting.