Hi Hans, I would recommend using the custRequestItem for the story, the implementation can be simple enough by using a service to create the header and item in a single call and a view entity could could them back to you as a single record. Conceptually what you really have is a customer request with a single item.
I don't like the idea of modifying the data model when it is already quite capable of meeting your needs. Regards, Scott On 11/03/2010, at 7:19 PM, Hans Bakker wrote: > At the moment i am looking to create a customer service component. > > The usage of the custRequest entity in this case never will need > custRequestItem's > > The long description field called 'story' is however only available in > the custRequestItem and not on the header. > > In order to simplify the implementation i would like to have the story > field also on the header in order not to have to use a 'dummy' > custRequestItem to use the story field. > > Any objections? > > -- > Ofbiz on twitter: http://twitter.com/apache_ofbiz > Myself on twitter: http://twitter.com/hansbak > Antwebsystems.com: Quality services for competitive rates. >
smime.p7s
Description: S/MIME cryptographic signature
