By Larry Caylor - 6/7/2006
In the v 1.41 6/6/2006 release the “Search for a Class Type” window in Object Mapper no longer locates enums within a business object. You can still type in the enum name in the Custom Data Type field and everything works okay. -Larry
|
By StrataFrame Team - 6/8/2006
Working on it, Larry. I'll see if I can't get it done before the update this morning that should fix your other DbNull problem.
|
By StrataFrame Team - 6/8/2006
OK, it will now find the ***FieldNames enumeration and other nested enumerations within classes in your solution. You will, however, have to build the partial class for a new business object at least once before the search window will find the FieldNames enumeration for that business object (otherwise, it hasn't been created, yet).
|
By StrataFrame Team - 6/8/2006
The update has been posted to the MyAccount area. This update fixes the issue described here as well as the InvalidCast exception you're receiving when you add a new record.
|
By Larry Caylor - 6/8/2006
Ben, OM is finding the enums within my project and I really like the customization wizard. It really simplifies the process of applying customizations to a group of fields. With this release I’ve noticed something new. I’ve created some complex business objects that contain a nested SF BO. I created a base BO and marked it as MustInherit. Then within my complex object I create a new nested class that inherits from my base class. The previous version of OM did not ‘see’ the nested class while this version does. Since I only want to map the base class I just left the inherited BO un-configured and rebuilt everything. OM prints out some warning and error message but everything works okay. If I go ahead and configure the nested class a Designer file is created. Any idea what .Net will do with the extra designer file? I would assume that the compiler would use the inherited files and the additional file created by OM would be ignored. -Larry
|
By StrataFrame Team - 6/8/2006
Actually, the designer file for the MustInherit object will be used. So, if there are properties in that designer file, then they will appear on all downstream objects. Also, any configuration changes to make within the component designer will affect all downstream objects (unless you override them downstream) because the InitializeComponent() method within the MustInherit object will be called, just like all the others. So, your best bet is probably going to be to just leave the business object unconfigured and ignore the warning. Or map the business object to a DDT profile table that doesn't have any fields, then you won't have to worry about the fields showing up in inherited objects.
|
By Larry Caylor - 6/8/2006
Ben,I just tried compiling a project with the 'extra' designer file and it creates a bunch of compiler errors. Just leaving the nested class un-configured sounds like the easiest solution. -Larry
|
By StrataFrame Team - 6/8/2006
Hehe, yeah, probably is the best solution.
|
By Keith Chisarik - 8/28/2006
Is this problem back?
Nothing at all happens in the BO Mapper search screen and when trying to use an unum with a combobox, the "Compiling list of available enums" just hangs there and the search screen dissappears.
Thanks.
|
By Trent L. Taylor - 8/28/2006
I think I found and fixed this problem today. It has to do when a namespace if not provided for a class. This is more prevalent in C#, but occurs in both languages. The problem is that the DTE environment is not providing a namespace and we were expecting one. I beleive this problem is resolved for good. We will try to get something on the web by the end of next week (we are all out of town this week  ).
|
By Keith Chisarik - 8/28/2006
So what might be a workaround?
|
By Trent L. Taylor - 8/28/2006
Try this...I don't think there will be any side effects. If so, you can get back to ground zero easy enough since you have that pre-release install from the training class.Drag the attached file into the GAC (c:\windows\assembly). Then go back into Visual Studio and the BO Mapper and see if the error persisits. Be sure to close down all VS instances before doing this.
|