Object Mapper


Author
Message
Larry Caylor
Larry Caylor
StrataFrame VIP (1.8K reputation)StrataFrame VIP (1.8K reputation)StrataFrame VIP (1.8K reputation)StrataFrame VIP (1.8K reputation)StrataFrame VIP (1.8K reputation)StrataFrame VIP (1.8K reputation)StrataFrame VIP (1.8K reputation)StrataFrame VIP (1.8K reputation)StrataFrame VIP (1.8K reputation)
Group: Awaiting Activation
Posts: 592, Visits: 3.7K

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

Reply
StrataFrame Team
S
StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)
Group: StrataFrame Developers
Posts: 3K, Visits: 2.5K
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.
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search