G'day

I've just had a frustrating few minutes trying to sort out why the business object mapper wouldn't let me configure a business object. It would go through the motions of letting me choose a source (an SQL Server 2005 view in this case), it would let me override the primary key, but when I said OK to all this the BO still showed with a red cross on the left hand side of the BOM with no fields shown on the other side.

After stopping and starting Visual Studio, and trying other brute force and ignorance tactics, I eventually discovered I had another BO of the same name in a different project within the solution. When I deleted the other BO (I hope I didn't need it), the BOM allowed me to configure the remaining one as normal.

I'm willing to admit that my stupidity was a contributing factor, but an error message would be nice.

Peter

Yeah, your BOs must have also been in the same namespace.  We did make a change a while back that allows BOs of the same name, but in different name spaces, to appear within the Mapper.  But we can add this to the list so that it is more apparent.  Thanks for the info.