Bug Tracker Incident #15645
Tested in xTuple version 3.8.0 Beta : Issue is fixed
A simpler reproduction:
Note: this is a uniqueness constraint, not a foreign key constraint, that's being violated.
More information: I received this error because the employee record I was trying to save had a null value in the Employee Number field--and a previously created employee record also had a null value in the Employee Number field.
Suggestion: If foreign key errors can be shown as a result of this condition, then perhaps Employee Number should be a required field on the employee screen?
Get the following db error saving a new employee record:
ERROR: duplicate key value violates unique constraint "emp_emp_number_key"
Steps to reproduce:
Open TTOYS CRM account
|Project||XTUPLEAPPS||Ported From Mantis||x|
SubscribersYou do not have permission to view subscribers.
No history available