c2c-oerpscenario team mailing list archive

["Daniel Watkins \(credativ\)" <676443@xxxxxxxxxxxxxxxxxx>]

Hi Saz,

Thanks for the speedy response.  I think I've failed to describe our
requirements properly, as neither of those solutions will actually work
for us.

The unique identifiers will not just be a number, they need to be able
to contain characters as well.  As such, we cannot use the orthodox 'id'
field.

Furthermore, we need to be able to modify the name of an Opportunity,
but the unique identifier needs to be immutable.  So we can't use the
Name field, because only one of those two requirements could remain
true.

I'm happy if this remains a Won't Fix, but I wanted to make sure that
you fully understood our reasoning behind the change before it stayed
like that forever.  As I say, we're going to be making this change
anyway, it's just a case of whether it will be of benefit to the
community at large.


Thanks again,

Dan

-- 
crm.case has no Code field
https://bugs.launchpad.net/bugs/676443
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Addons Modules: Won't Fix

Bug description:
Our client deals with many opportunities, often from the same client, at the same time.  We would like to create and store an un-editable identifier for each Opportunity whilst still having an editable Name field.  We think that a Code field would be the best option for this, as with Partners.

If we make this change, is it likely to be upstreamable?