We could also have a store option to let visible internal names and then use
them in that case (a bit convoluted maybe ;o)
Jacques
From: "Jacopo Cappellato" <[EMAIL PROTECTED]>
Scott, thanks for your comment... I understand your point of view.
The other options we have, if both productName and descriptions are
null:
1) put the productId in the itemDescription (but it seems not a good
option to me) or
2) fix the code to work well with a null itemDescription
Or we may require that when we create/update the product, the
productName is set (directly or thru the content... but that would be
trickier)
Hmmmm... I'm not sure which one is the best approach... probably #2
Jacopo
On May 20, 2008, at 9:16 PM, David E Jones wrote:
Yes, this is a good point. We probably shouldn't populate something
the customer sees with text from that field.
-David
On May 20, 2008, at 12:38 PM, Scott Gray wrote:
Hi Jacopo
It doesn't really bother me that much, but it seems funny to me
that the
system would use something explicitly defined as internal for
customer
facing pages. As a user I would expect that the customer would
never see
the contents of that field.
Regards
Scott
2008/5/21 Jacopo Cappellato <[EMAIL PROTECTED]>:
Hi all,
I've noticed that the OrderItem.itemDescription is only set if the
product's productName is available; I would like to add code so
that, if the
productName is not set, then the internalName is used.
I need this because the OrderItem.itemDescription seems to be
required by
some screens and some of the return procedures (I got errors
trying to
return orders with null itemDescriptions).
Is it ok?
Jacopo
