"User hits "Create Product List" button. and he then sees a list of all of the products with unchecked checbox beside each product."

 

Assume the "products with unchecked checkboxes" were in a grid.  This grid is bound to some entity list (business objects).  This entity list would NOT be the same entity list generated from the database.  We would essentially create business objects to support our UI needs and then "adapt" that to the business objects that we ORM'ed.  Am I understanding correctly?

 

Assuming that is true, then

1.  whenever the schema changes, we would have to update the mapper.

2.  Would we derive our UI centric entities from entity list, so we can get some of the benefits of DevForce binding?

 

Thanks for your patience on this.

 

Sincerely,

Dan

 

Once you have created the table for the parent filter table and the child filter itable n the database, you would then typically open the ORM Tool to create mapping between the database tables and the Parent and Child Entity.

 

Some ORM Tools allow you to start from a desgn, and they will generate tables in the database.  In DevForce, you almost akways start with the database first.

 

Once you have created a Parent and a Child Entity and mapped these entities in the ORM Tool, you can then build a UI that can create any number of Parent and Child Entities.  For example, let us say that you want to build a UI that will allow a user to build any number of Product Lists.  User hits "Create Product List" button. and he then sees a list of all of the products with unchecked checbox beside each product.  The user then checks the checkbox for products 1, 4, 7, 10, 11, and 14.  The user then hits the "Save Product List" button, and is prompted for a name.  The UI then creates the Product List.

Thanks for the reply.

 

You replied "create a parent filter with a user-specified name.  Also create a child filter for all of the possible children, e.g. 1, 3,7,11,14."  The parent and child filter you are referring to sound like entities we would code.  Are these entities generated using the ORM tool on top of the Filter and FilteredItems tables?  or are these entities we create manually and they know how to interact with entities ORM'ed against the Filter and FilteredItems tables?

 

I am hoping for some more guidance.

 

Given the database design shown, would I use the ORM tool to map the Filter and FilteredItems tables?  If i do map them, then there is a disconnect between the way I want the UI to work and the way the BO is designed.  The BO's would be mapped around a nornalized database.

 

So, to make the UI work like we want, I am thinking I need another set of BO's that sit on top of the ORM'ed BO.  If this is correct, then is there a recommended best practice to how to code this?

 

Thanks,

Dan

In another form, user can pick a filter.  Once he/she picks a filter,  create an EntityList using the filter.

 

One final piece of advice: Don't use a view.  Views are usually read-only.