Lewis Rosenberg
Forum Replies Created
-
Hello @fionalawsonsfinest-com ,
We created a modification where we capture “Lost Sales.” We have a table where every order line item is written to. Shipments and Invoices update this table. We created a “Cancel Order” function so if there is a back order that won’t be shipped, we cancel the order and update the table with qty and amount remaining (not shipped). This allows us to track orders accepted vs. fulfilment and “Lost Sales.”
-
Lanham’s Demand Planning does forecasting and SmartForecast from SmartCorp also integrates with BC/NAV.
https://www.lanhamassoc.com/demand-planning-extension.htm
https://smartcorp.com/microsoft-dynamics-ax-bc-365-nav-integration-inventory-management-planning/ -
Here FINALLY was the solution:
-
Hello Elizabeth!
The textbook answer is to create a new item with tracking turned on or rename the current item and then recreate the item number you are using. Of course, that will split your history and an item rename can take a long time.
A developer can help you turn tracking on but first you must remove all inventory and remove the item from all open orders, etc. After that a developer can write a quick process report to turn on tracking. Then you can add all of your inventory back into the system, including tracking information that was not in the system before and then you can add the item back to any orders.
-
Hello @becky-kaiserselect-cs-com ,
I just tested this in BC14 and BC22 and confirm that they behave differently. BC22 does not allow different column layouts as far as I can tell for different saved filtered lists.
In BC14 (using the RTC), I was able to have a different column layout for different saved filtered views. After creating the views I logged into the BC14 Modern (web) client and the column layouts were still different for my two different saved views from the same page. I did not try creating the saved filtered views in the modern client.
-
BC14 On Prem.
Our production and test environments share a Service Tier Server and a SQL server, but we have different SQL databases for both.
To refresh test, I use a RapidStart Configuration to export some setup tables from test that contain file export paths, etc., then a take a producion backup, restore it to the test SQL database and then import my setup files back to test using the configuration packages.
I have another business unit that I am supporting on NAV 2017. The have separate Service Tier and SQL server for production and test. We refresh test using the same process that I described above.
