I 'm trying to use Navigated event of Business Object to do business with other business object. But I've found that BusinessBindingSource Navigates internally and so this event is raised for every record of Business Object.

What can I do to cancel or catch this condition to go on doing my business in the navigated event of business object.

You are more than likely using a BBS and have it bound to a grid.  There is already a reported issue which we have on our list to fix for this particular scenario.  The BBS does not raise the navigated event for each row.  However, the Navigated event SHOULD get raised on the business object that is wrapped in the BBS.  You can run the BusinessBindingSource sample to see how to manage the Navigated event when wrapped in a BBS.

I've understood your explanation.

My case is related with the code like below.

DevexGrid.DataSource = bsCustomers ;

When this line was executed, Many navigation events were fired. I've coded the navigated event in component itself. But I've noticed that in your example it is coded in Form-Level.

I'll deal with many business objects and the solution must be in component-level ?

Is there a way to make this work ? It may require writing more lines of code. It does not matter.

I will see if I can reproduce your behavior.  I will have to setup a DevExpress grid.  It may be a couple of days before I have a chance to try and set this up, but I will add it to my list.  Thanks.

Have you investigated the case ?

Not yet...busy week.

What about this week ?

I know that there are developers using the DevExpress grid in many different shops.  I also know that the DevExpress grid behaves somewhat differently than the DataGridView and the Infragistics UltraGrid since DevExpress when down their own path and have a different base inherited class.  So I already know that their grid treats the IBindingList ListChanged event slightly different than everyone else...so this is not really an SF issue.  However, if you want to create me a small sample that reproduces your particular problem, I will take a look at it.  I have not had any issues with any of my tests, so if you could provide a sample that would probably be the best way to go.

I've solved this issue in my component with a property on a BusinessBase Object. This property holds the previous (last navigated) id of the parent object. I'm controlling the changes in that property then navigation logic comes after.

Since the topic is internal, It will be handled generally. I think so.

But If I need related information to this topic, I 'll produce the case with sample.

For this time, I 'll will go on with my solution.

Thanks.