I'm trying to populate a combo box via a fill method of a business object.  When I click the "..." button of the PopulationDataSourceSettings property, I get the following error when SF is searching for all of the Business Objects:

ConstraintException
  Column 'value' is constrained to be unique.  Value 'BBS.Biz.Base.AuditBO' is already present.
Source     : System.Data
Stack Trace: 
   at System.Data.UniqueConstraint.CheckConstraint(DataRow row, DataRowAction action)
   at System.Data.DataTable.RaiseRowChanging(DataRowChangeEventArgs args, DataRow eRow, DataRowAction eAction, Boolean fireEvent)
   at System.Data.DataTable.SetNewRecordWorker(DataRow row, Int32 proposedRecord, DataRowAction action, Boolean isInMerge, Int32 position, Boolean fireEvent, Exception& deferredException)
   at System.Data.DataTable.InsertRow(DataRow row, Int32 proposedID, Int32 pos, Boolean fireEvent)
   at System.Data.DataRowCollection.Add(DataRow row)
   at MicroFour.StrataFrame.Extensibility.ListPopulationEditorDialog.ᜂ()
   at MicroFour.StrataFrame.Extensibility.ListPopulationEditorDialog.ᜁ(Object A_0, EventArgs A_1)

After I close the error message, the SF dialog is there, but with no Business Objects or methods to choose from.  Can someone please advise on what might be causing this error? Thanks in advance.

Randy,

Taking a second look at your error, it may be that you don't have the correct SF assemblies or something in that route.  If you have updated your copy of SF, make sure you also update the SF database from the installation, you can do this as many times as you want, just reinstall SF and select the checkbox to update your SF database. 

If that is the case, download the latest beta release which is pretty stable from the Posted Release forum.

P.S.

At this point I am just guessing based on the error, I am sure Trent or somebody else from SF Team will jump in and give you a direct answer, but there is nothing wrong with trying to reinstall SF.

Edhy Rijo

Well, the problem is that you have two business objects with the exact same name and namespace within your project.  It sounds like you have a reference within your application that has a BO with this name and namespace and then another within the project itself.  That is the only way I think that this could actually happen.  Regardless, you will need to resolve this within your application otherwise you are going to have a lot of issues with ambiguous references.