You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ofbiz.apache.org by Christian Carlow <ch...@gmail.com> on 2014/01/13 17:30:32 UTC
How to store manufacturer product name different than one given by
customer?
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.
Re: How to store manufacturer product name different than one given
by customer?
Posted by Pierre Smits <pi...@gmail.com>.
You are correct in stating this.
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:48 PM, Christian Carlow <
christian.carlow@gmail.com> wrote:
> Also, the productName field is not included on the Product edit page.
> Instead it has to be set on the Product Content page along with the
> descriptions.
>
>
Re: How to store manufacturer product name different than one given
by customer?
Posted by Christian Carlow <ch...@gmail.com>.
Also, the productName field is not included on the Product edit page.
Instead it has to be set on the Product Content page along with the
descriptions.
On 01/13/2014 10:45 AM, Christian Carlow 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.
>
Re: How to store manufacturer product name different than one given
by customer?
Posted by Christian Carlow <ch...@gmail.com>.
Thanks for the clarification Jacques. The name the company assigns to
the customer part it intends to manufacture will be stored in brandName
field instead of productName eliminating the need to add the productName
field to the lookup.
On 01/19/2014 05:30 AM, Jacques Le Roux wrote:
> I don't remember if I answered yet, but I see no harms adding a productName field in Product lookup which could be used for your purpose (I don't mean to ad it OOTB)
> Note that the DMRB defines the brandName (a feature subtype) as a marketing name which can be different from the manufacturer's name (Nike being the manufacturer for instance)
>
> Jacques
>
> On Thursday, January 16, 2014 5:30 PM, christian.carlow@gmail.com wrote
>> This nabble thread about brand names is somewhat related to this issue:
>> http://ofbiz.135035.n4.nabble.com/Is-brands-supported-in-ofbiz-td3090415.html
>>
>> Again the internalName must be set to the name the customer assigns the
>> product because its the only required field of the product entity and
>> the internal company does not assign a manufacturing name until the
>> customer orders the product. So the company references the internalName
>> (customer assigned) when quoting but often references the manufacturing
>> name for remaining processes (ordering, production runs). I'm still not
>> exactly sure where the manufacturing name should be stored.
>>
>> The only fields that appear in the productId lookup are the productId,
>> internalName, and brandName so it seems the manufacturing name should be
>> stored in the brandName field but it seems like a company name such as
>> Nike is meant to go in that field. If values like 'Nike' are meant to
>> be stored in the brandName field then it seems necessary to add an
>> additional field to store the name that the internal company
>> manufacturing the part assigns which should be added to the product
>> lookup dropdown results.
>>
>> Can anyone clarify the purpose of the brandName field?
>>
>> On 01/13/2014 02:02 PM, Christian Carlow wrote:
>>> Here's the problem with the productId lookup field excluding the
>>> productName field from the search.
>>>
>>> The company assigns their manufacturing name (internalName) after it
>>> is ordered for manufacturing. If it never gets ordered then the
>>> company never assigns it a manufacturing/internal name. Because the
>>> company still needs to reference the customer name of products for
>>> quotes, it seems having another search field such as productName is
>>> necessary for the users to select the customer products before ever
>>> being ordered.
>>>
>>> On 01/13/2014 01:40 PM, Christian Carlow wrote:
>>>> Thanks Pierre,
>>>>
>>>> Shouldn't productName be included in the productId lookup field
>>>> query? I noticed its stored as a text field rather than a
>>>> varchar(100) like the internalName field which could cause lookup
>>>> problems...
>>>>
>>>> On 01/13/2014 12:16 PM, Pierre Smits wrote:
>>>>> 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.carlow@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.
Re: How to store manufacturer product name different than one given
by customer?
Posted by Jacques Le Roux <ja...@les7arts.com>.
I don't remember if I answered yet, but I see no harms adding a productName field in Product lookup which could be used for your purpose (I don't mean to ad it OOTB)
Note that the DMRB defines the brandName (a feature subtype) as a marketing name which can be different from the manufacturer's name (Nike being the manufacturer for instance)
Jacques
On Thursday, January 16, 2014 5:30 PM, christian.carlow@gmail.com wrote
> This nabble thread about brand names is somewhat related to this issue:
> http://ofbiz.135035.n4.nabble.com/Is-brands-supported-in-ofbiz-td3090415.html
>
> Again the internalName must be set to the name the customer assigns the
> product because its the only required field of the product entity and
> the internal company does not assign a manufacturing name until the
> customer orders the product. So the company references the internalName
> (customer assigned) when quoting but often references the manufacturing
> name for remaining processes (ordering, production runs). I'm still not
> exactly sure where the manufacturing name should be stored.
>
> The only fields that appear in the productId lookup are the productId,
> internalName, and brandName so it seems the manufacturing name should be
> stored in the brandName field but it seems like a company name such as
> Nike is meant to go in that field. If values like 'Nike' are meant to
> be stored in the brandName field then it seems necessary to add an
> additional field to store the name that the internal company
> manufacturing the part assigns which should be added to the product
> lookup dropdown results.
>
> Can anyone clarify the purpose of the brandName field?
>
> On 01/13/2014 02:02 PM, Christian Carlow wrote:
>> Here's the problem with the productId lookup field excluding the
>> productName field from the search.
>>
>> The company assigns their manufacturing name (internalName) after it
>> is ordered for manufacturing. If it never gets ordered then the
>> company never assigns it a manufacturing/internal name. Because the
>> company still needs to reference the customer name of products for
>> quotes, it seems having another search field such as productName is
>> necessary for the users to select the customer products before ever
>> being ordered.
>>
>> On 01/13/2014 01:40 PM, Christian Carlow wrote:
>>> Thanks Pierre,
>>>
>>> Shouldn't productName be included in the productId lookup field
>>> query? I noticed its stored as a text field rather than a
>>> varchar(100) like the internalName field which could cause lookup
>>> problems...
>>>
>>> On 01/13/2014 12:16 PM, Pierre Smits wrote:
>>>> 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.carlow@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.
Re: How to store manufacturer product name different than one given
by customer?
Posted by Christian Carlow <ch...@gmail.com>.
This nabble thread about brand names is somewhat related to this issue:
http://ofbiz.135035.n4.nabble.com/Is-brands-supported-in-ofbiz-td3090415.html
Again the internalName must be set to the name the customer assigns the
product because its the only required field of the product entity and
the internal company does not assign a manufacturing name until the
customer orders the product. So the company references the internalName
(customer assigned) when quoting but often references the manufacturing
name for remaining processes (ordering, production runs). I'm still not
exactly sure where the manufacturing name should be stored.
The only fields that appear in the productId lookup are the productId,
internalName, and brandName so it seems the manufacturing name should be
stored in the brandName field but it seems like a company name such as
Nike is meant to go in that field. If values like 'Nike' are meant to
be stored in the brandName field then it seems necessary to add an
additional field to store the name that the internal company
manufacturing the part assigns which should be added to the product
lookup dropdown results.
Can anyone clarify the purpose of the brandName field?
On 01/13/2014 02:02 PM, Christian Carlow wrote:
> Here's the problem with the productId lookup field excluding the
> productName field from the search.
>
> The company assigns their manufacturing name (internalName) after it
> is ordered for manufacturing. If it never gets ordered then the
> company never assigns it a manufacturing/internal name. Because the
> company still needs to reference the customer name of products for
> quotes, it seems having another search field such as productName is
> necessary for the users to select the customer products before ever
> being ordered.
>
> On 01/13/2014 01:40 PM, Christian Carlow wrote:
>> Thanks Pierre,
>>
>> Shouldn't productName be included in the productId lookup field
>> query? I noticed its stored as a text field rather than a
>> varchar(100) like the internalName field which could cause lookup
>> problems...
>>
>> On 01/13/2014 12:16 PM, Pierre Smits wrote:
>>> 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.carlow@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.
>>>>>
>>>>
>>
>
Re: How to store manufacturer product name different than one given
by customer?
Posted by Christian Carlow <ch...@gmail.com>.
Here's the problem with the productId lookup field excluding the
productName field from the search.
The company assigns their manufacturing name (internalName) after it is
ordered for manufacturing. If it never gets ordered then the company
never assigns it a manufacturing/internal name. Because the company
still needs to reference the customer name of products for quotes, it
seems having another search field such as productName is necessary for
the users to select the customer products before ever being ordered.
On 01/13/2014 01:40 PM, Christian Carlow wrote:
> Thanks Pierre,
>
> Shouldn't productName be included in the productId lookup field
> query? I noticed its stored as a text field rather than a
> varchar(100) like the internalName field which could cause lookup
> problems...
>
> On 01/13/2014 12:16 PM, Pierre Smits wrote:
>> 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.carlow@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.
>>>>
>>>
>
Re: How to store manufacturer product name different than one given
by customer?
Posted by Christian Carlow <ch...@gmail.com>.
Thanks Pierre,
Shouldn't productName be included in the productId lookup field query?
I noticed its stored as a text field rather than a varchar(100) like the
internalName field which could cause lookup problems...
On 01/13/2014 12:16 PM, Pierre Smits wrote:
> 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.carlow@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.
>>>
>>
Re: How to store manufacturer product name different than one given
by customer?
Posted by Pierre Smits <pi...@gmail.com>.
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.carlow@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.
>>
>
>
Re: How to store manufacturer product name different than one given
by customer?
Posted by Christian Carlow <ch...@gmail.com>.
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.