CustomersBO.OrdersBO.OrderItemsBO.ItemPrice

How can I do that for SF Business Object?

Paul

I have added a custom property to my customer BO just like you outlined.  In my application, I have the CustomersBO.SalesOrdersBO being assigned to the BusinessObject property of a BusinessBindingSource.  On the CustomersBO.Navigated event, I simply swap out the related BO:

OrdersBBS.BusinessObject = customersBO.CustomerOrders;

Works like a charm with the DevEx XtraGrid control.  To setup the control, I temporarily add a SalesOrdersBO to the form.  Assign it to the BBS, then work out how I want the grid to look.  After that, I simply remove the SalesOrderBO.  I am sure something similar could be done with the next level of BOs, too.

This StrataFrame stuff is rather cool!

While writing my response, you posted something even cooler!!    I shall be using that!

Bill

Hi Greg,

Thanks, but one more question, at some point I need to add code to make the ParentBO property in synch with the current record, where and how to do this?

I understand that in my Parent BO I will add a property to the ChildBO, but I want it to be in synch with the current selected parent record.  Also I don't have plans to use this for binding, just to get access to related child record for some custom functions and methods I will have in the BOs.

Hi Bill,

In your case, how do you make the SalesOrdersBO in synch with the CustomerBO? so when you make a reference to a field in the CustomersBO.SalesOrdersBO.ItemPrice it will give you the price of the current selected CustomerBO record.

[Browsable(false),
BusinessFieldDisplayInEditor(),
Description("Customer Orders"),
DesignerSerializationVisibility(DesignerSerializationVisibility.Hidden)]
public SalesOrdersBO CustomerOrders
{
    get
    {
        SalesOrdersBO mSalesOrders = new SalesOrdersBO();
        mSalesOrders.FillAllOrdersByCustomer(this.CustIndex);
        return mSalesOrders;
    }
}

I've tweaked this whole thing several times.  I am sure that I will tweak it again.  Always finding new, more efficient ways to use StrataFrame.

Bill

1.) In the parent business objects current data table refilled event, call the child tables fill by parent method.

2.)Either set the auto filter option or filter the record yourself in the parents navigate event. just remember you have filter on it will bite you.

Or

1.) Requery the db in the parents navigated event childbo.fillbyparentpk(myparent.pk)

I will start playing with the info provided right now.....

And I added this property to my Function GetCustomBindablePropertyDescriptors().  It was really easy, even though during a debug session I can not really see any property of the PolicyBO.InsuranceCompany object, I would get something like this in the watch window:

Also I have to be careful when to use any property of that object since it may not have any data and would throw errors, so I do this:

I am sure, there should be something I could add to the property code to avoid having to keep testing for the Me.PolicyBO1.InsuranceCompany.Count

Thanks again to all of you for pointing me to the right path and if there is a way to improve this, please do not hesitate to let me know.

Glad it is working for you...I'll keep my eyes pealed (peeled?) here in case someone does offer a better way of handling this.

Have a great weekend!
Bill

I am sure, there should be something I could add to the property code to avoid having to keep testing for the Me.PolicyBO1.InsuranceCompany.Count

Thinking about that, is there a way to have something like the VFP command SCATTER MEMVAR BLANK? that way I could test for the BO.count in the ParentBO and if count = 0, just create a new empty row. 

What do you think about it?

Thanks, the code is pretty understandable.  About the third option, this where a function like SCATTER MEMVAR BLANK would do the trick on initializing the empty row, unless I am just missing the simple point on using the BO.NewRow() to have a blank row with no values, so any use of its property will not throw an error.  I will test that.

Also thanks for the points about not using the descriptors, you are right and these are not needed for this kind of properties.

All the time I simply get amazed with how functionality that seems pretty difficult or hard to do are accomplish in the .NET world and of course SF with a couple of line of code.

This is getting better when changing the code as follow:

I now get an error when trying to use this property in a code like this:

Look at the attached image for the error: NullReferenceException was unhandled by user code.  Object reference not set to an instance of an object.

What I understand about this error is that I would need to create an instance of this object in order to use this property, while when using the original method there was not need to do that, guess because previous method was always creating an instance of the class with this code:

Dim loLookupBO As New InsuranceCompanyBO

So far, the error has nothing to do with setting values to the created new row.  When using BO.NewRow() SF will populate it with the default values which are good enough in my case.

In order to make it work I added a "New" command to initialize the Private BO variable like this:

Then I made some changes to the property code to make sure the BO is filled all the time, like this:

So far the code above is working fine.