Home > SI5 Documentation > User Guide > Known Issues > Creating Products within Projects – Issue with QuickLinks

Creating Products within Projects – Issue with QuickLinks

Creating Products within Projects – Issue with QuickLinks

 

There is no “Add New Product” function within our project interfaces based off of any existing product. The function of adding new products to your MasterTable database based off of an existing product is in the Manage My Product Data Interface (MMPD), the Copy Product function. However, many clients use the work around detailed below to add new products based off of existing products to their MasterTable from within a project interface:
 
  1. Opening the Products Properties for an existing product within the PDM of a project.
  2. Changing the Model number, not with the attempt to edit the existing product but with the intent of creating a new product based off of the existing products.
  3. Clicking Save on the Product Properties form and choosing NO when asked to update the product to MasterTable.
  4. Re-opening the Product Properties window, clicking Save, and then choosing YES to update the MasterTable. They are then prompted the product does not exist in the MasterTable and asked if they want to create a new product. 

 

DO NOT FOLLOW THE STEPS ABOVE IF YOU ARE QUICKLINKS USER

 

Changes were made in Service Pack 3 (SP3) to the behavior of products within projects when one or more of the following three fields are updated: Manufacturer, Model, Category.   Below details the previous behavior, the new behavior, and the bug found for the new behavior.

Old Behavior, Prior to SP3

Scenario:

You open up the Product Properties of a product within the Project DataMatrix (PDM) of a project and make changes to any the Manufacturer, Model, or Category. You then click the Save button and chose Yes to update the changes to the MasterTable.

Outcome:

You would be prompted that the product does not exist in the MasterTable and you were asked if you wanted to create a new product in your MasterTable.

Why this behavior was changed in SP3:

Editing a product within a project was intended for just that, editing. It was not intended to create new products in your SI5 MasterTable database. Since products are uniquely identified in the MasterTable database by a combination of the Manufacturer, Model, and Category fields, changes to these fields would cause a new product to be created in your MasterTable when your only intent was re-categorize or correct a Model number (add a dash, remove spaces, etc.).  This created duplicate products in your SI5 database which caused confusion and clutter. Clients who use QuickLinks were then finding that since a new product was created in the MasterTable after their edits that they would have to then re-assign QuickBooks Item Numbers to these “new” products.

SP3 Behavior

Scenario (same as above):

You open up the Product Properties of a product within the PDM of a project and make changes to any the Manufacturer, Model, or Category. You then click the Save button and chose Yes to update the changes to the MasterTable.

Outcome:

The changes are saved to the current product in the MasterTable, you are not prompted that the product does not exist in the MasterTable.

Bug:

The bug we found with this is that within the project, the “new” product created in step 4 above retains the QuickBooks Item Number of the “old” product rather than having a blank QB Item Number that requires an assignment. This will mean that if you attempt to push over a Sales Order that contains this “new” product to QuickBooks in an Estimate/Invoice/PO that the “new” product will transfer over with the QB Item Number for the “old” product.

Until Bug is Fixed:

Do not create new products within a project as shown in the steps 1-4 above. If you wish to add a new product to your MasterTable database, open the MMPD interface and use the Copy function to copy an existing product and make your modifications there. Then add the new product to the project.
You must to post a comment.
Last modified
17:02, 26 Nov 2013

Tags

This page has no custom tags.

Classifications

This page has no classifications.