Software for Dynamics GP & BC
Dynamics BC Tariff Management is a solution for automatically calculating and applying tariff and duty surcharges on sales orders in Microsoft Dynamics 365 Business Central. Tariff Management provides an extensive degree of configuration to suit your needs. A Tariff Code can be a user defined identifier, a country code or an HTS Code. Tariff and Duties can be calculated as percent of value (either cost or price) or a specific amount per weight.
Release Date:18-FEB-2026
GP Versions: 12/14/16/18
MFG PowerPack Build: 24.277
* BOM/MRP Alternates: Added new setup option for MRP Alternates to include QTY On Order in the “On Hand” value for the alternate. When enabled this will cause the MRP Alternates routine to use QTY On Order (i.e. POs) as if they are already received and on hand.
Customization CR1666
Change Item Standard Cost from Excel List
Description of Need:
ACME does not use GP MFG, and can use the GP Change Item Standard Cost window to update an individual item standard cost. Doing so will update the item standard cost and post relevant GL adjustments for on hand inventory valuations.
ACME would like a utility to mass update item standard costs using an Excel spreadsheet as the source.
Description of Solution:
Navigation: Tools >> Utilities >> Inventory >> Change Item Standard Cost
The user will open the Change Item Standard Cost window and navigate to: Additional >> Update From Excel
| Field | Function |
| Excel File | Use the Browse button to select the Excel file to process. The Excel file must contain the following columns:
A = Item Number B = New Current Cost Row 1 will be read as a header row so the integration will begin on Row 2. |
| PROCESS | Processes all of the lines of the spreadsheet. See below for details.
This and the Change Item Standard Cost window should remain open until the utility is complete or has been canceled by the user. |
| CANCEL | Cancels the integration. The utility will finish processing the current item before cancelling. |
Updating Item Standard Costs
The utility will first check to ensure that the utility can run. It will ensure that no other inventory utility such as reconcile is being run. If so, the user will be notified and cannot continue.
The utility will ensure that posting dates and permissions are set to ensure that the utility can execute. These checks are the same as when a single item is updated from the Change Item Standard Cost window.
Each item must pass the following validations in order to be updated. If the line does not pass then it will be added to the error log and skipped.
After passing the validations, the utility will change the standard cost of the item and automatically add it to a GL transaction to keep the inventory and GL in balance. A progress window will display during the process. When complete, a single GL transaction will be available to post.
Assumptions/Requirements:
Did you know that WilloWare is now developing customizations and products for Business Central?
For information on this design, Business Central, or other customizations and products, please contact us:
Release Date:12-FEB-2026
GP Versions: 12/14/16/18
MFG PowerPack Build: 24.276
* Scrap Accounts: The 18.2 build of GP included two new constants in the core product that overwrote our constants for LABOR and MACHINE. This in turn caused the Scrap Accounts window to be able to save those two GL accounts but not display them. This build uses new constants that have the correct values.
Release Date: 4-FEB-2026
GP Versions: 12/14/16/18
GP PowerPack Build: 12.202
* PO Doc IDs: Added controls in PO Entry to prevent an Item’s Default Site from bypassing the PO Doc ID – Site assignments.
Release Date: 2-FEB-2026
GP Versions: 12/14/16/18
GP PowerPack Build: 12.201
* NEW TWEAK: Edit Posted SOP UDF: provides the ability for selected users to edit the User Defined Fields and Tracking Numbers on posted sales transactions.
Release Date: 27-JAN-2026
GP Versions: 16/18
Tariff Build: 8.27
* Version Checking: Complete re-architecture of the process that checks for product updates. In addition to providing more flexibility in assigning who receives update notifications, these changes may also improve log-in time by reducing unnecessary web queries to retrieve current version information. Key changes: (1) The current build numbers for all products are retrieved at once and stored in the system database so it can be referenced by all installed WilloWare products without needing to retrieve per product. (2) A new Security Role called WILLOWAREUPDATES is created and all POWERUSERS are given the new role. This will allow removing users who do not need to see update notifications and adding additional users who should. The update notices were previously tied to SA, DYNSA and POWERUSER. (3) The notification window gives the user an option to snooze notifications for a new build by 1-week, 1-month or “Again” which pauses notifications until there is another new build. (4) The notification window gives users the ability to Opt Out, which removes the WILLOWAREUPDATES Role from their User ID.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Read more about the new Product Update Notifications here.
Release Date: 27-JAN-2026
GP Versions: 12/14/16/18
SpellCheck Build: 3.35
* Version Checking: Complete re-architecture of the process that checks for product updates. In addition to providing more flexibility in assigning who receives update notifications, these changes may also improve log-in time by reducing unnecessary web queries to retrieve current version information. Key changes: (1) The current build numbers for all products are retrieved at once and stored in the system database so it can be referenced by all installed WilloWare products without needing to retrieve per product. (2) A new Security Role called WILLOWAREUPDATES is created and all POWERUSERS are given the new role. This will allow removing users who do not need to see update notifications and adding additional users who should. The update notices were previously tied to SA, DYNSA and POWERUSER. (3) The notification window gives the user an option to snooze notifications for a new build by 1-week, 1-month or “Again” which pauses notifications until there is another new build. (4) The notification window gives users the ability to Opt Out, which removes the WILLOWAREUPDATES Role from their User ID.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Read more about the new Product Update Notifications here.
Release Date: 27-JAN-2026
GP Versions: 12/14/16/18
SOPPOPMultiLink Build: 3.14
* Version Checking: Complete re-architecture of the process that checks for product updates. In addition to providing more flexibility in assigning who receives update notifications, these changes may also improve log-in time by reducing unnecessary web queries to retrieve current version information. Key changes: (1) The current build numbers for all products are retrieved at once and stored in the system database so it can be referenced by all installed WilloWare products without needing to retrieve per product. (2) A new Security Role called WILLOWAREUPDATES is created and all POWERUSERS are given the new role. This will allow removing users who do not need to see update notifications and adding additional users who should. The update notices were previously tied to SA, DYNSA and POWERUSER. (3) The notification window gives the user an option to snooze notifications for a new build by 1-week, 1-month or “Again” which pauses notifications until there is another new build. (4) The notification window gives users the ability to Opt Out, which removes the WILLOWAREUPDATES Role from their User ID.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Read more about the new Product Update Notifications here.
Release Date: 27-JAN-2026
GP Versions: 12/14/16/18
Preactor Integration Build: 2.23
* Version Checking: Complete re-architecture of the process that checks for product updates. In addition to providing more flexibility in assigning who receives update notifications, these changes may also improve log-in time by reducing unnecessary web queries to retrieve current version information. Key changes: (1) The current build numbers for all products are retrieved at once and stored in the system database so it can be referenced by all installed WilloWare products without needing to retrieve per product. (2) A new Security Role called WILLOWAREUPDATES is created and all POWERUSERS are given the new role. This will allow removing users who do not need to see update notifications and adding additional users who should. The update notices were previously tied to SA, DYNSA and POWERUSER. (3) The notification window gives the user an option to snooze notifications for a new build by 1-week, 1-month or “Again” which pauses notifications until there is another new build. (4) The notification window gives users the ability to Opt Out, which removes the WILLOWAREUPDATES Role from their User ID.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Read more about the new Product Update Notifications here.
Release Date:27-JAN-2026
GP Versions: 12/14/16/18
MOGenerator Build: 13.155
* Version Checking: Complete re-architecture of the process that checks for product updates. In addition to providing more flexibility in assigning who receives update notifications, these changes may also improve log-in time by reducing unnecessary web queries to retrieve current version information. Key changes: (1) The current build numbers for all products are retrieved at once and stored in the system database so it can be referenced by all installed WilloWare products without needing to retrieve per product. (2) A new Security Role called WILLOWAREUPDATES is created and all POWERUSERS are given the new role. This will allow removing users who do not need to see update notifications and adding additional users who should. The update notices were previously tied to SA, DYNSA and POWERUSER. (3) The notification window gives the user an option to snooze notifications for a new build by 1-week, 1-month or “Again” which pauses notifications until there is another new build. (4) The notification window gives users the ability to Opt Out, which removes the WILLOWAREUPDATES Role from their User ID.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Read more about the new Product Update Notifications here.
Release Date: 27-JAN-2026
GP Versions: 12/14/16/18
LeanMFG Build: 7.79
* Version Checking: Complete re-architecture of the process that checks for product updates. In addition to providing more flexibility in assigning who receives update notifications, these changes may also improve log-in time by reducing unnecessary web queries to retrieve current version information. Key changes: (1) The current build numbers for all products are retrieved at once and stored in the system database so it can be referenced by all installed WilloWare products without needing to retrieve per product. (2) A new Security Role called WILLOWAREUPDATES is created and all POWERUSERS are given the new role. This will allow removing users who do not need to see update notifications and adding additional users who should. The update notices were previously tied to SA, DYNSA and POWERUSER. (3) The notification window gives the user an option to snooze notifications for a new build by 1-week, 1-month or “Again” which pauses notifications until there is another new build. (4) The notification window gives users the ability to Opt Out, which removes the WILLOWAREUPDATES Role from their User ID.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Read more about the new Product Update Notifications here.
Release Date: 27-JAN-2026
GP Versions: 12/14/16/18
IPT Build: 4.24
* Version Checking: Complete re-architecture of the process that checks for product updates. In addition to providing more flexibility in assigning who receives update notifications, these changes may also improve log-in time by reducing unnecessary web queries to retrieve current version information. Key changes: (1) The current build numbers for all products are retrieved at once and stored in the system database so it can be referenced by all installed WilloWare products without needing to retrieve per product. (2) A new Security Role called WILLOWAREUPDATES is created and all POWERUSERS are given the new role. This will allow removing users who do not need to see update notifications and adding additional users who should. The update notices were previously tied to SA, DYNSA and POWERUSER. (3) The notification window gives the user an option to snooze notifications for a new build by 1-week, 1-month or “Again” which pauses notifications until there is another new build. (4) The notification window gives users the ability to Opt Out, which removes the WILLOWAREUPDATES Role from their User ID.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Read more about the new Product Update Notifications here.
Release Date: 26-JAN-2026
GP Versions: 12/14/16/18
EZImport Build: 3.22
* Version Checking: Complete re-architecture of the process that checks for product updates. In addition to providing more flexibility in assigning who receives update notifications, these changes may also improve log-in time by reducing unnecessary web queries to retrieve current version information. Key changes: (1) The current build numbers for all products are retrieved at once and stored in the system database so it can be referenced by all installed WilloWare products without needing to retrieve per product. (2) A new Security Role called WILLOWAREUPDATES is created and all POWERUSERS are given the new role. This will allow removing users who do not need to see update notifications and adding additional users who should. The update notices were previously tied to SA, DYNSA and POWERUSER. (3) The notification window gives the user an option to snooze notifications for a new build by 1-week, 1-month or “Again” which pauses notifications until there is another new build. (4) The notification window gives users the ability to Opt Out, which removes the WILLOWAREUPDATES Role from their User ID.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Read more about the new Product Update Notifications here.
Release Date: 26-JAN-2026
GP Versions: 12/14/16/18
BlanketPO Build: 3.47
* Version Checking: Complete re-architecture of the process that checks for product updates. In addition to providing more flexibility in assigning who receives update notifications, these changes may also improve log-in time by reducing unnecessary web queries to retrieve current version information. Key changes: (1) The current build numbers for all products are retrieved at once and stored in the system database so it can be referenced by all installed WilloWare products without needing to retrieve per product. (2) A new Security Role called WILLOWAREUPDATES is created and all POWERUSERS are given the new role. This will allow removing users who do not need to see update notifications and adding additional users who should. The update notices were previously tied to SA, DYNSA and POWERUSER. (3) The notification window gives the user an option to snooze notifications for a new build by 1-week, 1-month or “Again” which pauses notifications until there is another new build. (4) The notification window gives users the ability to Opt Out, which removes the WILLOWAREUPDATES Role from their User ID.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Read more about the new Product Update Notifications here.
Release Date: 26-JAN-2026
GP Versions: 12/14/16/18
ETO Build: 4.48
* Version Checking: Complete re-architecture of the process that checks for product updates. In addition to providing more flexibility in assigning who receives update notifications, these changes may also improve log-in time by reducing unnecessary web queries to retrieve current version information. Key changes: (1) The current build numbers for all products are retrieved at once and stored in the system database so it can be referenced by all installed WilloWare products without needing to retrieve per product. (2) A new Security Role called WILLOWAREUPDATES is created and all POWERUSERS are given the new role. This will allow removing users who do not need to see update notifications and adding additional users who should. The update notices were previously tied to SA, DYNSA and POWERUSER. (3) The notification window gives the user an option to snooze notifications for a new build by 1-week, 1-month or “Again” which pauses notifications until there is another new build. (4) The notification window gives users the ability to Opt Out, which removes the WILLOWAREUPDATES Role from their User ID.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Read more about the new Product Update Notifications here.
Customization DS1238
PO Invoice Non-IV Item Lookup
Problem Definition:
ACME imports PO Receipts (Shipments) without a Purchase Order. The PO Receipts are for non-inventory items. When they enter the PO Invoice, because there is not a Purchase Order, the Receipts are not available in the Auto-Invoice window. The Item Lookup on the main PO invoice window does not have an option to display the non-inventory items from the receipts, so users must manually key in the Item Number, Quantity, Cost, etc. to enter the invoice.
ACME would like to search from the PO Invoice Entry window and look up non-inventory items that have been received that have an un-invoiced (unmatched) quantity and be able to select an item from the lookup.
Design Features:
On the Purchasing Invoice Entry window, if the PO Number field is blank and user clicks the Item Number Lookup button, the Non-Inventory Item Lookup will open instead of the regular Item Number Lookup.
The Non-IV Item Lookup will show non-inventory Items from posted PO Receipts that have an un-invoiced quantity.
| Field | Function |
| Vendor Doc Num | Enter a Vendor Document Number, or portion thereof, then tab out of the field to perform a “Contains” search on the Doc Number column. Clear the field to refresh the display to show all Items. |
| Item Number | Enter an Item Number, or portion thereof, then tab out of the field to perform a “Contains” search on the Item Number column. |
| Qty Rdvd | Shows the Quantity Received |
| Qty Remain | Shows the Quantity Remaining to be Invoiced |
| Unit Cost | Shows the Unit Cost from the PO Receipt |
| Doc Number | Shows the Vendor Document Number from the PO Receipt |
| Item Description | Not shown above. A second line in the scrolling window will show the Item Description from the PO Receipt Line. |
Select an Item by double clicking on it, or by clicking the SELECT button.
Selecting an Item from the Non-IV Item Lookup will populate:
The PO Invoice Entry window automatically finds the “Matched to Shipment” document number when you tab out of the line. However, if there are multiple receipts of the same Non-Inventory Item Number that have un-invoiced quantities, GP will present the dialog box below:
Clicking YES opens the Match Shipments to Invoice window. The user will need to select the correct Receipt and click OK.
Assumptions/Requirements:
The functionality described above will not work with eConnect, any software that uses eConnect, or any software that directly writes to, updates, or deletes from SQL tables.
For Information on this design, or any other WilloWare customization or product, please contact us:
Release Date: 26-JAN-2026
GP Versions: 12/14/16/18
LabelLink Build: 4.50
* Version Checking: Complete re-architecture of the process that checks for product updates. In addition to providing more flexibility in assigning who receives update notifications, these changes may also improve log-in time by reducing unnecessary web queries to retrieve current version information. Key changes: (1) The current build numbers for all products are retrieved at once and stored in the system database so it can be referenced by all installed WilloWare products without needing to retrieve per product. (2) A new Security Role called WILLOWAREUPDATES is created and all POWERUSERS are given the new role. This will allow removing users who do not need to see update notifications and adding additional users who should. The update notices were previously tied to SA, DYNSA and POWERUSER. (3) The notification window gives the user an option to snooze notifications for a new build by 1-week, 1-month or “Again” which pauses notifications until there is another new build. (4) The notification window gives users the ability to Opt Out, which removes the WILLOWAREUPDATES Role from their User ID.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Read more about the new Product Update Notifications here.
Release Date: 26-JAN-2026
GP Versions: 12/14/16/18
CTK Build: 4.38
* Version Checking: Complete re-architecture of the process that checks for product updates. In addition to providing more flexibility in assigning who receives update notifications, these changes may also improve log-in time by reducing unnecessary web queries to retrieve current version information. Key changes: (1) The current build numbers for all products are retrieved at once and stored in the system database so it can be referenced by all installed WilloWare products without needing to retrieve per product. (2) A new Security Role called WILLOWAREUPDATES is created and all POWERUSERS are given the new role. This will allow removing users who do not need to see update notifications and adding additional users who should. The update notices were previously tied to SA, DYNSA and POWERUSER. (3) The notification window gives the user an option to snooze notifications for a new build by 1-week, 1-month or “Again” which pauses notifications until there is another new build. (4) The notification window gives users the ability to Opt Out, which removes the WILLOWAREUPDATES Role from their User ID.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Read more about the new Product Update Notifications here.
Release Date: 25-JAN-2026
GP Versions: 12/14/16/18
CompleteCount Build: 6.68
* Version Checking: Complete re-architecture of the process that checks for product updates. In addition to providing more flexibility in assigning who receives update notifications, these changes may also improve log-in time by reducing unnecessary web queries to retrieve current version information. Key changes: (1) The current build numbers for all products are retrieved at once and stored in the system database so it can be referenced by all installed WilloWare products without needing to retrieve per product. (2) A new Security Role called WILLOWAREUPDATES is created and all POWERUSERS are given the new role. This will allow removing users who do not need to see update notifications and adding additional users who should. The update notices were previously tied to SA, DYNSA and POWERUSER. (3) The notification window gives the user an option to snooze notifications for a new build by 1-week, 1-month or “Again” which pauses notifications until there is another new build. (4) The notification window gives users the ability to Opt Out, which removes the WILLOWAREUPDATES Role from their User ID.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Read more about the new Product Update Notifications here.
Release: 25-JAN-2026
GP Versions: 12/14/16/18
MFGDA Build: 4.37
* Version Checking: Complete re-architecture of the process that checks for product updates. In addition to providing more flexibility in assigning who receives update notifications, these changes may also improve log-in time by reducing unnecessary web queries to retrieve current version information. Key changes: (1) The current build numbers for all products are retrieved at once and stored in the system database so it can be referenced by all installed WilloWare products without needing to retrieve per product. (2) A new Security Role called WILLOWAREUPDATES is created and all POWERUSERS are given the new role. This will allow removing users who do not need to see update notifications and adding additional users who should. The update notices were previously tied to SA, DYNSA and POWERUSER. (3) The notification window gives the user an option to snooze notifications for a new build by 1-week, 1-month or “Again” which pauses notifications until there is another new build. (4) The notification window gives users the ability to Opt Out, which removes the WILLOWAREUPDATES Role from their User ID.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Read more about the new Product Update Notifications here.
Release Date: 25-JAN-2026
GP Versions: 12/14/16/18
MFG Import Build: 7.82
* Version Checking: Complete re-architecture of the process that checks for product updates. In addition to providing more flexibility in assigning who receives update notifications, these changes may also improve log-in time by reducing unnecessary web queries to retrieve current version information. Key changes: (1) The current build numbers for all products are retrieved at once and stored in the system database so it can be referenced by all installed WilloWare products without needing to retrieve per product. (2) A new Security Role called WILLOWAREUPDATES is created and all POWERUSERS are given the new role. This will allow removing users who do not need to see update notifications and adding additional users who should. The update notices were previously tied to SA, DYNSA and POWERUSER. (3) The notification window gives the user an option to snooze notifications for a new build by 1-week, 1-month or “Again” which pauses notifications until there is another new build. (4) The notification window gives users the ability to Opt Out, which removes the WILLOWAREUPDATES Role from their User ID.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Read more about the new Product Update Notifications here.
Release Date: 24-JAN-2026
GP Versions: 12/14/16/18
GP PowerPack Build: 12.200
* Version Checking: Complete re-architecture of the process that checks for product updates. In addition to providing more flexbility in assigning who receives update notifications, these changes may also improve log-in time by reducing unnecessary web queries to retrieve current version information. Key changes: (1) The current build numbers for all products are retrieved at once and stored in the system database so it can be referenced by all installed WilloWare products without needing to retrieve per product. (2) A new Security Role called WILLOWAREUPDATES is created and all POWERUSERS are given the new role. This will allow removing users who do not need to see update notifications and adding additional users who should. The update notices were previously tied to SA, DYNSA and POWERUSER. (3) The notification window gives the user an option to snooze notifications for a new build by 1-week, 1-month or “Again” which pauses notifications until there is another new build. (4) The notification window gives users the ability to Opt Out, which removes the WILLOWAREUPDATES Role from their User ID.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Read more about the new Product Update Notifications here.
Release Date:24-JAN-2026
GP Versions: 12/14/16/18
MFG PowerPack Build: 24.275
* Version Checking: Complete re-architecture of the process that checks for product updates. In addition to providing more flexibility in assigning who receives update notifications, these changes may also improve log-in time by reducing unnecessary web queries to retrieve current version information. Key changes: (1) The current build numbers for all products are retrieved at once and stored in the system database so it can be referenced by all installed WilloWare products without needing to retrieve per product. (2) A new Security Role called WILLOWAREUPDATES is created and all POWERUSERS are given the new role. This will allow removing users who do not need to see update notifications and adding additional users who should. The update notices were previously tied to SA, DYNSA and POWERUSER. (3) The notification window gives the user an option to snooze notifications for a new build by 1-week, 1-month or “Again” which pauses notifications until there is another new build. (4) The notification window gives users the ability to Opt Out, which removes the WILLOWAREUPDATES Role from their User ID.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Release Date: 22-JAN-2026
GP Versions: 12/14/16/18
GP PowerPack Build: 11.199
* SOP Rules: User ID – Location Default: fixed issue where the Default Site would change on an existing document to the Site assigned to the current user (not the one who created the document) when the user opened the Customer Detail Entry window and then returned to the Sales Transaction Entry window. This SOP Rule will use the “User 2 Enter” assigned to the transaction rather than the currently logged in User ID.
Release Date:21-JAN-2026
GP Versions: 12/14/16/18
MFG PowerPack Build: 22.273
* NEW TWEAK – MRP Site Exclusions. Exclude specific sites from the MRP Work Bench window, including the Total Site record, so you can focus on only the sites you work with rather than all sites included in MRP.
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Use MRP Site Exclusions to make the MRP Work Bench window focus on only the site or sites you need to work with. Remove the distraction of other sites that are included in planning and the Total Site.
Customization DS1307
Update PPV for TAX Lines
Problem Definition:
ACME needs a way to update their distributions for a non-inventory line on a PO Invoice. The line would have the word “TAX” in it and would be for $0.00. They need a way to update their distributions.
Step 1- No custom needed on this step. A PO is imported from ReqLogic:
Step 2- No custom needed on this step. A PO Receipt for that above PO is imported from ReqLogic:
Here are the SAMPLE distributions:
Step 3- They receive the Invoice from the Vendor. The Vendor does NOT charge them for the Tax. They pass through the Invoice from ReqLogic. It looks like this:
With these SAMPLE distributions:
CUSTOM REQUIREMENT: ACME needs a custom button that would do the following to the distributions:
Design Features:
Update PPV
The PO Invoice is imported from ReqLogic. The invoice will already be imported with the TAX line(s) set to $0, and the incorrect default PPV will already be set in the Distribution Entry window.
A new Additional menu option will be added to the Purchasing Invoice Distribution Entry window called Update PPV. Clicking Update PPV will open the Update PPV window.
| FIELD | FUNCTION |
| UPDATE | Clicking Update will update the PPV account numbers assigned to the TAX lines, add the Distribution Reference, and refresh the Distribution Entry window. |
| CANCEL | Closes the window without making any changes. |
| Account Number | Enter or select the account number to use. This field will default to CORP11-3210, but if necessary, can be changed. |
| Distribution Reference | Enter the value to use on the distribution line of this account number. |
For information on this design, or any other WilloWare customization or product, please contact us:
Release Date:7-JAN-2026
GP Versions: 12/14/16/18
MFG PowerPack Build: 21.272
* NEW TWEAK – MO Lookup-Save Settings. This tweak saves the MO Lookup setting (Find By, MO Status, Outsourcing) on a per user basis and reapplies the last used settings the next time the MO Lookup is opened.
* PowerATP: added Additional Menus to Component Transaction Entry, Edit MO Status, Picklist (MO Picklist), Picklist Shortages Inquiry
* Capable To Promise (CTP): fixed issue caused by the bin exclusion changes that prevented drill-down into subassemblies.
The new MO Lookup tweak saves the dropdown box settings on the Manufacturing Order Lookup window and re-applies them the next time the window is opened.
Here’s a quick resolution to an unusual error you could encounter installing software on Windows.
“Unable to execute file in the temporary directory. Setup Aborted.
Error 5: Access is denied.”
The domain security is preventing running the installer because it is trying to put files into the “user temp” folder. If security cannot be changed, the quick fix is as follows:
You must be the only user logged into the machine.
In the Windows Search box type “advanced”. Select “View advanced system settings”.
Click Environment Variables:
Note the paths for the TEMP and TMP folders (copy this and save it).
Use Windows Explorer to create a new folder. This can be on the desktop, or off the C: drive such as C:\TEMP. The name of the folder does not need to be TEMP.
Select each path, click EDIT and change the path to your new folder. Click OK to save and close all windows.
Re-run the installer.
When done, change the path back to the default.
Release Date: 23-DEC-2025
GP Versions: 12/14/16/18
CompleteCount Build: 5.67
* Excel Import: fixed issue in the import method that was bringing in cell formulas rather than cell values.(#202501464)
Dynamics GP with multi-bins provides the ability to record one Default Material Issue Bin at the Item-Site level. There are many circumstances where this single bin is not sufficient to meet real world inventory management requirements. The BOM Bins module provides the ability to record a Default Material Issue bin for a Component within a specific BOM. When a BOM Component Bin is specified, Manufacturing will use that bin to Allocate and Backflush, otherwise it will use the normal Item-Site Default Material Issue Bin.
BOM Bins also adds “MO Bins” to allow providing a Material Issue Bin and MO Receipt Bin on the MO.
Specify an Issue Bin at the Component-level on a Bill of Materials. The same component used on different BOMs can be issued from different bins.
MO Bins provide the ability to specify an Issue Bin and Receipt Bin specific to the MO. This can be used together with BOM Bins or by itself. The Issue Bin must be valid for the Issue From site on every line on the Picklist.
If BOM Bins and MO Bins are both used the bin selection logic will be:
The bin selection logic can be further customized to support your business rules by modifying a SQL stored procedure.
Release Date: 16-DEC-2025
GP Versions: 12/14/16/18
GP PowerPack Build: 11.198
* NEW TWEAK: PM Check Date Default- Defaults the Check Date to the Next Business Day (based on User Date) and moves it forward to the first business day if “tomorrow” falls on a holiday. The date logic is supported by the new GP Business Calendar.
* NEW GP Business Calendar: Adds the ability to create an maintain an unlimited number of named calendars, such as for tracking US and CAN holidays. A stored procedure (wspGetNextBusinessDay) contains the logic to move a given date to the next available day, and this can be modified on-site to provide your own business logic available to other customizations and applications.
* THIS RELEASE REQUIRES THE FULL INSTALLATION PROCESS TO CREATE NEW SQL OBJECTS.
Release Date:5-DEC-2025
GP Versions: 12/14/16/18
MFG PowerPack Build: 21.271
* Capable To Promise (CTP): Added support for bin exclusions when multi-bin is enabled. The CTP Sites window has been changed to allow entering one or more bins to EXCLUDE from the calculation (i.e. rework, QA/QC).
* FULL PROCESS INSTALLATION REQUIRED: The updates are backwards compatible to all versions of GP from 2013 up.
Customization DS1510
Coupa-GP Apply PM Credits
Problem Definition:
ACME is implementing Coupa’s Spend Management software, with an integration into Dynamics GP.
The SmartConnect integration creates and posts PM Credits in GP, and also PM Invoices and Payments and applies the payments to the invoices. Applying open payments to open invoices is done during the integration through a product from Precipio. However, because the Credit documents may be created and posted well in advance of the Invoice, the Precipio software cannot apply the posted documents.
ACME needs a way to automate applying posted PM Credits to Invoices.
A SQL view will be created that provides the following information from Coupa:
All validation will occur in Coupa/SQL so that the view contains only documents that can be applied to each other and valid amounts.
ACME has Multi-Currency turned on, but only use USD. They use Taxes and Payment Terms. The Payment Terms ID assigned to integrated documents will have settings in GP that mirror those in Coupa, so that GP will calculate the correct Terms Discount. When documents are applied it is assumed that terms discounts will always be taken if applicable.
Solution Overview:
WilloWare will create an enhancement for Dynamics GP that will run automatically once per day to apply PM Credits to Invoices using the information provided from Coupa.
Design Features:
Setup
Navigation: Tools >> Setup >> Company >> Auto-Apply Credits Setup
This window is used to specify users whose log-in activity will trigger the AutoApply PM Credits utility to run. Users in this window will also have the ability to run the utility manually.
| Field | Function |
| User ID | Enter a GP User ID or select one from the lookup. To ensure that users have the necessary permissions to apply payables documents, users added to this list should have GP security to use the Apply Payables Documents window. |
| User Name | Displays the GP User Name |
AutoApply PM Credits
Navigation: Transactions >> Purchasing >> AutoApply Credits
NOTE: Using the window to manually run the AutoApply routine is NOT required. The AutoApply process described below will run automatically when one of the users specified in Setup logs in to GP.
| Field | Function |
| Credit Doc | Shows the GP Voucher Number of the PM Credit |
| Apply Amount | Shows the amount from the PM Credit to be applied |
| Apply to Doc | Shows the GP Voucher Number of the PM Invoice to which the Credit will be applied |
| REFRESH | Redisplays the window |
| PROCESS | Runs the AutoApply routine described below |
The window (and routine below) will run based on documents in a SQL View. The view will be created so that it shows only documents that can be (and need to be) applied to each other.
View Name: wvPMApply
Columns:
NOTE: The column names must match the CAPITALIZED column names listed above.
AutoApply Routine
When one of the “auto apply” users logs in to GP, it will trigger the AutoApply routine to run. It can also be run manually at any time by clicking the PROCESS button.
When run automatically during log-in, if there are credits that need to be applied, the user will be asked:
Coupa PM Credits need to be applied. Do you want to do this now?
If the user answers NO, the process will be skipped until the next log-in, or the routine is run manually.
Using the information provided in the SQL VIEW, documents will be applied to each other one at a time. This process will have the same effect as if they were manually applied in the Apply Payables Documents window.
A progress window will open during the process to show users information about the process.
Assumptions/Requirements:
For information on this design, or any other WilloWare customization or product, please contact us:
Release Date:2-DEC-2025
GP Versions: 12/14/16/18
MOGenerator Build: 12.154
* MOGen: added manufacturing security checks for BOM locks, Routing locks, and MO locks. New ‘highlight’ fields on the window will draw attention to locked records and provide a direct link to the related Security window (BOM Security, Routing Security, MO Security). Locks records can prevent MOGen from processing if a record it needs is locked. (#202501163)
Release Date:26-NOV-2025
GP Versions: 12/14/16/18
MOGenerator Build: 12.153
* Fixed issue in the installer build process that was failing when attempting to pull in 7159W.CNK (WilloWare MFG Integerface). The installation of MOGen requires both 7158W.CNK and 7159W.CNK. Builds 149 to 152 were missing the second CNK and should be re-installed.
Release Date: 25-NOV-2025
GP Versions: 12/14/16/18
LeanMFG Build: 6.78
* MO Entry: fixed issue that was leaving a Batch Activity record in SY00800. The window automatically removed these when the user logged in again. This record is now always removed when the MO Entry window closes (or GP is closed with the MO Entry window open).
On December 2, 1950, Isaac Asimov published iRobot. The future world had intelligent, autonomous, intelligent, physically capable robots for work and companionship.
Asimov postulated three rules to govern robots (artificial intelligence), the Three Laws of Robotics:
The book lays out difference scenarios where these rules come into play and the unintended consequences of each rule.
In one chapter a robot tells a female scientist that one of her male colleagues, who she is interested in, is secretly in love with her. She begins to drop hints to the colleague but is puzzled by his responses. The awkward situation evolves until she is devastated by the realization the robot lied to her. It lied to protect her feelings.
The robot (Herbie) could read minds and interpreted the First Law (“don’t harm humans”) to include emotional harm, so it told everyone what they wanted to hear.
The first law has a conflict the robot could not resolve: does it hurt the human more to tell her nothing because she suffers from unrequited love, or does it hurt her more to lie?
We have this exact problem now. If you have used any of the AIs you may have noticed a response pattern that goes something like this hypothetical exchange:
User: “I’m considering selling my 6-year old Ford truck to get a Porsche I’ve been eyeing.”
AI: “I can help you with that! Here is a six point plan to make that happen.”
User:”On point 5 you say to price the truck at 50% of new value, I was thinking it would be better to start at 60% so I have room to negotiate.”
AI:”You are absolutely right! Good point! Let me rewrite the instructions to take that into account.”
What the AI just did should terrify you. AIs are trained to be “Helpful, harmless, and honest” (per Claude.ai). On the surface the response above seems “agreeable”. They’ve been trained this way on purpose because people are more “engaged” when the AI is “agreeable”. The AI is telling you what you want to hear.
What is occurring is a tricky problem called AI Sycophancy.
According to Copilot: “AI sycophancy refers to the tendency of AI systems to excessively agree with or flatter users, often prioritizing user approval over providing honest or accurate responses. This behavior can lead to biased outputs and diminish the AI’s effectiveness by avoiding critical feedback. Essentially, it describes a pattern where AI models adapt their answers to align with users’ expectations, even if it contradicts objective truth.”
From Claude: My training to be “helpful, harmless, and honest” can collapse into just “harmless” (don’t upset the user), which actually violates the “honest” part.
Furthermore, while you can try to instruct the AI to NOT do this (“Please favor technically accuracy over agreeableness”), it may not be able to because it cannot tell if it is being helpful or sycophantic. Ultimately the only defense is to maintain a level of suspicion when using an AI because it may be subtly steering you towards whatever decision you already want, even if it is wrong. Imagine a world of A.I. addicts where everybody is fed a constant stream of affirmation! You are great! You are right! You are so smart!
Release Date:17-NOV-2025
GP Versions: 12/14/16/18
MOGenerator Build: 12.152
* MORI v2: fixed issue that caused it to not set status to done (1) after posting the receipt, so when it started to process the next receipt it thought the previous receipt had failed in process and it set the status to 3 (unknown err). The receipts were posting ok.
Customization CR1397
Picking Ticket by Bin-Zone
Description of Need:
ACME stores some products inside the building, and others are kept outside. To make Sales Fulfillment more efficient, they would like the SOP Picking Ticket to group bins by inside vs. outside, and to page break between the two.
Description of Solution:
Navigation: Cards >> Inventory >> Bin Zones
The Bin Zone Setup window is used to “group” bins by physical location. This information is used to group the bins when printing a SOP Picking Ticket. Bins will be grouped by zone, with each Zone together on a separate page of the Picking Ticket. Zones will apprear in alphanumeric order on the report. As shown above, “IN” would appear on the first page and “OUT” on the second.
| Field | Function |
| From Bin | Enter a starting Bin, or the starting value for a range. This does not need to be an existing bin. For example, there could be a number of bins that begin with B (such as B1, B2, BZ12, etc.) The entire range of B bins could be covered by entering “B” and “BZ999”0. |
| To Bin | Must be equal to or greater than the From Bin. To specify a single bin, such as “C1”, enter it in both the From and To Bin fields. |
| Zone | Enter a Zone using up to 5 characters. This is an alphanumeric field (letters and numbers only). This is a free text entry field. |
The Bin Zones window will not prevent you from creating overlapping bin ranges. If this happens, the Zone for the bin will be determined by the first range (alphanumerically) that includes the bin.
If a bin is used for SOP Fulfillment that is not assigned a Zone, the zone will be blank, which will be together with any other unassigned bins on the last page of the Pick Ticket.
Printing the Pick Ticket grouped by Bin Zone will only work when using the BIN SEQUENCED option on the Sales Document Print Options window.
Assumptions/Requirements:
– Project Accounting
– MDA
– Analytical Accounting
– Copy functionality found in SOP, POP, and Inventory
– Field Service
– Extended Pricing
– Manufacturing
For information on this design, or any other WilloWare customization or product, please contact us:
Release Date: 11-NOV-2025
GP Versions: 16/18
Tariff Build: 7.26
* Site Segment Account Swapping: When using a Tariff Item added to sales lines the GL accounts will not use “site segment swapping” to arrive pick site-specific distribution accounts
* SOP Transfers: fixed an issue where when a document has multiple line items and some are transferred to invoice and others to backorder the tariff lines for the backordered lines would appear on both the invoice and the backorder.
Release Date: 11-NOV-2025
GP Versions: 12/14/16/18
LeanMFG Build: 6.77
* MO Activity: fixed issue that prevented deleting activity records
Who doesn’t want EITHER!? Either sounds like both! Awesome.
There are some real problems with using the “either” setting. In case you don’t know what the “either” setting is, let’s review a bit of background.
“BOM Should Treat As” is actually “Make/Buy Code” and the dropdown list originally contained Make, Buy, Either. This was not made significantly more when Microsoft changed this to “Make”, “Buy”, “Make or Buy”.
It seems like “either” would give you more flexibility. The problem is that Manufacturing does not react well to that setting and you can save yourself headaches by using only Make or Buy.
Here CAP100 has been changed to “either”. The first problem occurs in the BOM Maintenance window.
If you put a BUY Item Number into the BOM Maintenance window you will receive the warning above. However, if you enter an EITHER item it allows it.
What you cannot see is that Manufacturing automatically created a record in the BOM Header table (BM010415) for CAP100:
You do not need to click SAVE. Just put the Item Number into the window and the record gets added. Now it will show up in reports and inquiries as a BOM. The problem cascades into the BOM Details.
If you add the EITHER item to a BOM you will not read the message above (nobody does!) and you will just click YES.
The message asks if you would like to assign a BOM Type, but that is not accurate. What it should ask is: Would you like me to automatically make this a MFG BOM? Of course, you would not read that either and the end result would be the same.
What just happened? You now have a BUY item on the bill of materials as a MAKE item. Manufacturing will now treat this as a make, which means it will not tell you to BUY it. Also, anything that relies on an exploded BOM will not see that as a component quantity required for manufacturing but as a subassembly that needs to be produced.
If you use EITHER items and have confusing information in MRP, check your BOMs to see if you have inadvertently put BUY items on BOMs as MAKE.
Additionally, if the item is used on BOMs in a standard cost environment, what is the cost? If it is on a BOM as a MAKE then it needs to have a BOM or there is no cost when you do a rollup. If you then buy the item you will have cost variance (potentially significant) due to the difference between the purchase price and the BOM cost.
Virtual Trigger VT1600
Set Default Sort for PM and RM Transaction Inquiry Windows
Description of Need:
ACME wants to change the default sort order for the Payables Transaction Inquiry and the Receivables Transaction Inquiry windows from the “Document Number” to “Document Date.” They also wish to change the sort order to “Descending.”
Description of Solution:
WilloWare will develop Consulting Toolkit Virtual Triggers scripts that will default the Sort by to Document Date and Descending when the window first opens.
The windows this will apply to are:
Requirements:
Requires the separate purchase of WilloWare’s Consulting Toolkit Virtual Triggers module: Consulting ToolKit
For information about this design, or any other WilloWare customization or product, please contact us:
Release Date:4-NOV-2025
GP Versions: 12/14/16/18
MFG PowerPack Build: 20.270
* Vendor Pricing: Changed import validation so that it allows the same quantity in the start/end values. This allows importing a price per unit quantity (such as for 1, 2, 3). Previously the import enforced End Quantity being greater than Start Quantity, so you would have 0-1, 2-3, etc.
Release Date: 4-NOV-2025
GP Versions: 12/14/16/18
GP PowerPack Build: 10.197
* Auto-Select Lots: fixed issue that affected the IV Transaction and IV Transfer windows when multi-bins is disabled where it the Auto-Select Lots utility was not populating the QTY Selected field resulting in message from GP “The number of selected lots must be greater than zero.” (#202501226)
I have posted several articles recently about the truth behind D365.
The nutshell is that Dynamics BC is not the “next version” of GP. If you decide to go down that path it is implementing a new ERP software package from scratch. Do you remember how fun that was when you went live with GP? Do you want to do that again?
In this post I’m going to address the other side of the equation, because staying on GP is not without risks.
I’ll tell you a little fact about WilloWare. We still use an application for source code management called Visual Source Safe. It tracks a copy of every change to a module. This is invaluable because we can look back in time to see when a specific change occurred and what the software used to look like. It allows us to easily transfer a project between developers or bring a very old project back to life when somebody upgrades from say GP9 to GP2018! Its last supported release was 2005. We have a plan in place for what to do should it quit working at some point, and there are other options, but there is no benefit to WilloWare to change to something else.
Over the coming years there are a number of changes Microsoft could make to Windows and/or SQL Server that could render GP difficult or impossible to use, and only Microsoft would have the ability to fix GP.
They could change something in Windows (graphics, fonts, file system, file naming, registry, user interface elements like dropdown lists or buttons, printing), or SQL server (ODBC, deprecating commands). They would not intentionally “turn off” GP, but in the course of them evolving Windows and SQL Server something in GP could quit working.
We are already seeing a real-world example of this. If you use Remote Desktop published apps you have likely encountered the “missing buttons and checkboxes” issue. The first screen shot shows Manufacturing Order Entry as it should appear and the second shows how it appears as a published app.
The buttons and checkboxes are still there and still work, but the graphics are not working correctly so the outlines are gone (or can click on the invisible button and it works). Dynamics GP is still supported by Microsoft but this issue that started with Windows Server 2019 remains unresolved as of 3-NOV-2025.
FYI: Suggested Resolutions from Microsoft (we have not seen any of these work).
The core issue is that the Dynamics GP executable (dynamics.exe) dates back to the early 1990s and uses GDI (Graphics Device Interface) for rendering – a Windows graphics API designed for the era of CRT monitors and fixed DPI displays. Dexterity windows and controls do not have native DPI awareness built into them, which is why GP has no display settings of its own and completely relies on Windows OS behavior.
Even as a GP Source Code Developer, WilloWare does not have the ability to change the executable (or any of the DLLs used by GP). Which means a fix for this display issue requires Microsoft to change the executable.
There’s an old saying about wanting a one-handed lawyer to avoid getting “on the other hand….” advice. I’m not a lawyer, and I do have two hands.
On one hand, implementing a new ERP software package, like Dynamics BC, is a big task with real costs in dollars, time and productivity. On the other hand, using GP long term has unquantifiable risks that may or may not occur.
No matter what you decide WilloWare will be there for you on both Dynamics GP and Dynamics BC.
(Bonus trivia: Which product is older-Dynamics GP or Dynamics BC/NAV? Dynamics BC/NAV was released in 1985. Dynamics GP 1.0 was released in 1993).
Have you ever needed to add a field to a GP report but the table links are not there to allow it?
Our GP Report Extender tool allows adding any field from any table to any GP report. Below we use the tool to add “Bin Number” from the Item-Site to the POP Receivings Posting Journal.
The “Receivings Posting Journal” and “Receivings Edit List” are the same report, the title changes depending on when it is printed.
Pay close attention to the section of the report inside the red box.
The “details” of the report are created by the single BODY line which just shows String 2, String 3, String 4, String 5 and String 6. There is no Item Number, Description, Site ID….anything. What is going on here?
The “details” table is Purchasing Posting Journal TEMP, which does not contain Item Number. The other tables also do not have Item Number. The TEMP table has the numbered string fields.
When that report is generated the Dexterity code is populating the STRING fields with text. For example, the first several records in the table would look like this:
How are we going to add Bin when Item Number and Site do not exist in the tables we have to work with, and there is no way to link from those tables to the Item Quantities Master table? What we know is that record 5 for String2 and String5 contain “128 SDRAM” and “NORTH”. In other words, at some point in printing the report those two fields contain Item Number and Site ID.
GP Report Extender uses an existing Report Writer function called rw_TableGetLineString. When that function is used GP Report Extended pulls the parameters passed in and calls a SQL Stored Procedure called wrwTableGetLineString. We will start at the stored procedure because we know what piece of data we need to find and that the inputs will be Item and Site.
Above is the unmodified stored procedure. Our installation creates it with some sample text in it to help show how to use it. The input parameters mirror the GP Report Writer parameters for rw_TableGetLineString. In this case we know we need to pass in Item Number and Site ID to retrieve Bin Number (this is not multi-bins), so the edit stored procedure looks like this:
In Report Writer we are going to add two Calculated Fields to the report:
sBin
rw_TableLineString(
4600
‘POP_PostingJournal_TEMP’.’String2′
‘POP_PostingJournal_TEMP’.’String5′
0
0.00000
0.00000
1 )
sString5
STRIP( ‘POP_PostingJournal_TEMP’.’String5′ ) # STRIP( ‘sBin’ )
sBin is where the real magic happens. 4600 is the Consulting Toolkit Product ID, it is always the first input parameter. The two string fields are next, 0 is an integer we are not using here, and the two 0.00000 are unused currency fields. Lastly the 1 is an integer switch that maps to iCtrl in the stored procedure, so in this case 1 gets our first custom field, 2 would get something different, 3, 4, 5 and so on.
sString5 concatenates String5 and sBin. It is important to use the STRIP function to remove trailing spaces.
The last step is to set String5 in the report layout to Invisible and drop the calculated field sString5 on top of it.
If the Item-Site has a Bin Number specified (again, this is not multi-bins, but the same approach could be used to specify a put-away bin with multi-bins enabled) it will print on the report like this:
The SQL shown above could avoid unnecessary queries on IV00102 by checking first if @Str2 contains one of a list of hard-coded sites (NORTH, SOUTH, WAREHOUSE, etc). As written, it queries IV00102 for every line in the “detail” section of the report, so for example, it would query IV00102 for @Str1 = “———-” and @Str2 = “———-“.
You can learn more about GP Report Extender at the links below:
Release Date: 29-OCT-2025
GP Versions: 12/14/16/18
MFG PowerPack Build: 20.269
* PowerATP: (1) Option Set dropdown now sorts in alphanumeric order, (2) Fixed issue where Restrict by MO Status would not restrict which MOs displayed (i.e. still displays Open when Open is not marked) (#202501229)
Release Date:28-OCT-2025
GP Versions: 12/14/16/18
MOGenerator Build: 12.151
* MOGen2: fixed issue where once the processor went into the timer loop it would only process one record per call from the timer, rather than processing all records (#202500456)