0002804: Usernames for Org and Client cannot be same

Notes
(0003430) cromero (viewer) 2008-04-07 10:40 edited on: 2008-06-12 09:25	Logged In: YES user_id=1500614 Originator: NO The description of this bug is not specific enough . The information required for reproducing this bug is not in its description. Please make sure to specify: 1) Complete problem description 2) Environment details (Openbravo version, database type and OS) 3) Specific steps on how to reproduce the problem. For more information, pleas refer to: http://wiki.openbravo.com/wiki/index.php/Bug_Reporting_Guidelines [^] Please, reopen this bug adding the required details. Thank you. The Openbravo Team

(0003431) cromero (viewer) 2008-04-08 18:24 edited on: 2008-06-12 09:25	Logged In: YES user_id=1500614 Originator: NO This doesn't report a bug but a problem with the installation/application. Please, use the forums to try to solve this problem. Thank you very much. Openbravo team

(0003432) cromero (viewer) 2008-04-08 18:24 edited on: 2008-06-12 09:25	Logged In: YES user_id=1500614 Originator: NO The problem is not the name for the Organization and Client (look at the attached screenshot where I have created a Client with an Organization with the same name, "Prueba"). In my opinion, the problem is the accounting file used to create the Client. You can download the last version here: http://sourceforge.net/project/showfiles.php?group_id=162271&package_id=254937 [^] In the development version (trunk in the svn repository) you can also create a client without accounting file (it could have no sense if you are not going to use accounting later). File Added: Screenshot-0.png

(0003433) cromero (viewer) 2008-04-08 18:31 edited on: 2008-06-12 09:25	Logged In: YES user_id=1500614 Originator: NO Sorry, I was wrong

(0003434) cromero (viewer) 2008-04-08 18:32 edited on: 2008-06-12 09:25	Logged In: YES user_id=1500614 Originator: NO It should be verified or the error message should be more userfriendly

(0003435) cromero (viewer) 2008-05-21 18:16 edited on: 2008-06-12 09:25	Logged In: YES user_id=1500614 Originator: NO Now the error message is more user friendly: "Unique key repeated. You may check the data" And in the data you can see that restriction AD_USER_UN_USERNAME has been violated

(0006393) user71 2005-06-01 00:00 edited on: 2008-06-12 09:43	This bug was originally reported in SourceForge bug tracker and then migrated to Mantis. You can see the original bug report in: https://sourceforge.net/support/tracker.php?aid=1933299 [^]

Issue History
Date Modified	Username	Field	Change

Relationships [ Relation Graph ] [ Dependency Graph ]