> Ok, I've been looking at this module and it is saying that you need to assign > a unique id to each partner. I would have to do this for a lot of partner > records. I suppose I could just use raw sql and insert ascending values into > the field. How can I make the partner unique automatically. Wouldn't it be > better to use an auto sequenced field. Maybe the 'id' field be used instead > since it looks like it is auto sequenced. Any thoughts on this. Also newly > created partner records would need their uniqueness to be handled > automatically. Do we need to add anything to the create partner form?
I have used this for a while, I like to have all customers with a numeric ID (so they can access info via DTMF through phones etc) so find this essential. It is a UI addon (Unless this is changed in latest) and makes use of the "ref" partner field. The constraint is in the UI, not the DB. It really should be more integrated as I feel that it will be good for many users but no burden for those who do not use it. I guess it may be argued that the record "id" could be used for this field but I feel that there may be a time that this ref may need to be manipulated, or a user may want a prefix or other formatting for this field where the record "id" must be strictly maintained to retain the database integrity. Regarding the point on duplicate names, from using these systems for a while, it should always be avoided anyway, as confusion can be common but this does depend on how you run your business. I guess it should not be for Tiny to enforce best practises but maybe just recommend them, or provide configuration options on how this (and other rules) should be set. SM _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
