[ http://issues.apache.org/jira/browse/OFBIZ-547?page=comments#action_12461566 ] Chris Howe commented on OFBIZ-547: ----------------------------------
Thanks for looking at this Anil. There is an instance that this solution doesn't handle. Since the sequence-id-to-env simply retrieves a value based on a field in SequenceValueItem, and the database is unaware of it's importance, it is possible for the SequenceValueItem to be out of sync with the next non duplicated primary key value. This may occur in a deployment that does entity syncs or imports. Is this pattern already used, or are you suggesting it? Additionally, since you're suppressing the error from occurring, you may want to put something to the log file perhaps showing the entire FixedAsset record that was retrieved (but certainly not to the screen as the user may not have privilege to view that record). > Duplicate Id error on Create New FixedAsset > ------------------------------------------- > > Key: OFBIZ-547 > URL: http://issues.apache.org/jira/browse/OFBIZ-547 > Project: Apache OFBiz (The Open for Business Project) > Issue Type: Improvement > Components: accounting > Reporter: Anil K Patel > Attachments: FixedAssedIdDuplicateMessage.patch > > > While creating a New FixedAsset, if user enters FixedAssetId that already > exists in system, Unfriendly message is returned and existing fixedAsset is > opened in Edit mode. > 1) The error message should be easier to understand by user. > 2) Existing fixedAsset should not be opened in edit mode, this confuses user > with Idea that fixedAsset was created. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
