Home › Forums › Users › General User's Discussion ›

Product Description versus Name

Submitted by Geoffvet on Sun, 31/10/2010 - 10:13
in

Hi all,

When listing products in the product workspace I note that both Name and Product Description are identical. There does not seem to be a field that alters the Description in any of the data entry screens but perhaps Im missing something.

It would be useful if, especially in the case of services, if the description field allowed you to enter info to spell out details of a product/service's use or expanded details of a product that weren't needed if printing a report.

Cheers Geoff

 

Hi again,

Can anyone explain why Name & Product Description are the same.

Cheers Geoff

‹ Merchandise in Summary Product Description versus Name ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: Product Description versus Name

Submitted by dadmin on Sun, 07/11/2010 - 22:01.

Hi Geoff,

The product description field is hidden in the archetype for the products. It is also set to be derived from the product name in the archetypes.  I'm not sure of there is a reason for this- perhaps a use was not seen for the field at the time???

I'd never noticed the description field on products before, but it could be quite useful for putting info on when to charge one fee versus another for example.  

Matt Y.

Re: Product Description versus Name

Submitted by tony on Mon, 08/11/2010 - 07:42.

Hi Geoff and Matt,

Very easy to change field to not be derived and not be hidden so you can edit contents. Can do individually (Administration -> Archetypes) or, if everyone sees it being useful, happy to change for next release.

Cheers

Tony

Re: Product Description versus Name

Submitted by Geoffvet on Mon, 08/11/2010 - 18:47.

Thanks Tony & Matt,

Just what I was after and as you say Tony easy to change.

I have changed the fields for services and merchandise so the description field can expand on the name. Will let us spell out what a particular entry covers (very useful for services) and will be able to place a few directions or flag some products that cause us issues.

For medications Ive just sussed that invoices and labels are derived from different fields.

Personally I prefer label and invoice entries to be the same and as I have setup 'printed names' to be more succinct for labels (duhhh.. I didnt notice that the labels werent using these shortened fields probably because the Name was being truncated automatically on the label.)

 For us the actual name field holds the bottle size or other details we dont want on either label or invoice so will use 'printedName' in documents and labels as preferred by Sandra in earlier posts.

So getting back on topic - in the case of medications Ive kept with derived value but swapped in the 'printed name path' as I see it is a useful way of ensuring the product and product strength that end up on the label/invoice match the product name as they should - nice safety check.

Much Thanks

Geoff

Syndicate content