Christian, The productName field is intended for all your outbound documents, like order, shipping manifest and invoices. It is intended to display the commercial name of your product. The field internalName is intended like the field name is, for internal purposes.
Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Mon, Jan 13, 2014 at 5:45 PM, Christian Carlow < christian.car...@gmail.com> wrote: > I just realized that a productName field already exists in the Product > entity. Could someone explain the difference between this field and the > internalName field? Why is the productName field not included in the > product lookupField? Could my internalName=manufacturerName and > productName=customerName or visa versa? > > > On 01/13/2014 10:30 AM, Christian Carlow wrote: > >> Does anyone know how to store a manufacturer name for a product that >> differs from the customer purchasing? In this scenario, the customer >> designs the part and provides the specifications and the company >> manufactures raw materials to meet those specs. The name the customer >> gives the part typically matches the spec or drawing number but the company >> reassigns it to an internal job number. >> >> My users need to be able to select the product by either the customer or >> manufacturer name. I thought about storing the manufacturer product name >> in the brandName field but it seems like the name of a Party is meant to be >> stored in that field. >> >> In my previous email I asked if a revision field should exist in the >> Product entity for storing product revision numbers. If this is not a bad >> design choice then would it suffice to add a manufacturerName field to the >> Product entity as well for storing the given manufacturer name of a product? >> >> Previously I tried tracking the manufacturer name by naming Manufacturing >> Routes after the manufacturer name and related the part being manufactured >> to get the manufacturer name but this introduced too much complexity. The >> simple method would be having the field stored with the Product entity >> itself. >> > >
