This project has moved. For the latest updates, please go here.

Root Collection->Editable Child->Editable Child Collection->Editable Child

May 9, 2011 at 1:20 PM

Is this allowed:  Root Collection->Editable Child->Editable Child Collection->Editable Child .   When I try to generate this I get some errors.  I can leave off the Root Collection but it is kind of nice being able to save everything at once.

May 9, 2011 at 2:16 PM

I should say I get a warning not an error:

RegisterReceipt isn't root and has children; RegisterReceipt.EmployeePaymentList Loading Scheme should be "Self Load".

Just wondered if it is common practice to have this setup of if I should be tackling this another way.

Coordinator
May 9, 2011 at 3:52 PM

Hi Farmischer,

Can you describe your object hierarchy?

Like <root><1st level child><2nd level child><etc> stating for each level whether it's an object or a collection.

May 10, 2011 at 1:17 PM

<root> Collection Yes, I would like to do an Editable Root Collection: ParentCollection.

<1st level child> Object This would contain Editable Child called Parent.

<2nd level child> Collection The Parent would contain an Editable Child Collection called Child1Collection.

<3rd level child> Object The Child1Collection would contain an Editable Child called Child1.

Is this what you were asking me for?  If not let me know and I will try again.

Coordinator
May 11, 2011 at 12:21 AM
farkmischer wrote:

RegisterReceipt isn't root and has children; RegisterReceipt.EmployeePaymentList Loading Scheme should be "Self Load".

Please refer to http://cslagenfork.codeplex.com/workitem/356 as it explains the requirements of your use case.

Feel free to get back here and post if something isn't clear.