Prevent Duplicate Records
Prevent duplicate records:
- Customers/
- Products
- GL Accounts
- any of the configuration tables
- ...
Use unique indexes where appropriate.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
See also this blueprint:
https:/
04-04-2011 GraemeG
I think this needs a little more specification. What do we mean by unique. e.g. I absolutely want to have 2 entries called Loan from Bank X, or Lease for Car Y. The reason for this is that one must be reported as a current liability as it is due within 12 months, the other as a non-current as its balance is due later. Also I want 9 entries for Current Assets, as I have 9 companies, 7 of which are consolidating into an 8th. So really I am saying only account code (and absolute path in the case of duplicate name) should be unique, and then only for that one company. On the partner front there are a few scenarios as well where a duplicate name is foreseeable, esp in Multicompany Same for products, where I think uniqueness at Product Code level is desirable, but at name level too restrictive. Not to say it isn't needed, just that it needs more specification.
