Custom Field Property in BO Mapper


Author
Message
Trent Taylor
Trent Taylor
StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)StrataFrame Developer (10K reputation)
Group: StrataFrame Developers
Posts: 6.6K, Visits: 6.9K
Richard,

I guess I am little confused as to what youa re trying to accomplish.  You you elaborate a bit more?  Are you referring to the DDT or something else?

Richard Keller
Richard Keller
StrataFrame User (132 reputation)StrataFrame User (132 reputation)StrataFrame User (132 reputation)StrataFrame User (132 reputation)StrataFrame User (132 reputation)StrataFrame User (132 reputation)StrataFrame User (132 reputation)StrataFrame User (132 reputation)StrataFrame User (132 reputation)
Group: Forum Members
Posts: 84, Visits: 324
Basically, I'd like to expose my BO's and have the user be able to add fields at runtime.   Just like the old Data Dictionary days.   Think of the DDT being an integrated runtime designer.

Richard

StrataFrame Team
S
StrataFrame Developer (4.2K reputation)StrataFrame Developer (4.2K reputation)StrataFrame Developer (4.2K reputation)StrataFrame Developer (4.2K reputation)StrataFrame Developer (4.2K reputation)StrataFrame Developer (4.2K reputation)StrataFrame Developer (4.2K reputation)StrataFrame Developer (4.2K reputation)StrataFrame Developer (4.2K reputation)
Group: StrataFrame Developers
Posts: 3K, Visits: 2.5K
I don't think StrataFrame will be able to support that.  Yes, the customers could have access to the data structures through the DDT, but the structure of the business objects would not be able to change without using the BOMapper and recompiling the assemblies containing the business objects. 

You might be better off defining one table that containg data dictionary values...

ddv_pk
ddv_FieldName
ddv_FieldValue
ddv_pk_Parent

The FieldValue would be a variant data type to store whatever you place in it.  Then you could pull all of the values for a parent record in one query and add some sort of maintenance program to allow the end user to define the custom fields.

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