Hi,

I found that, BOAdd() doesn't filter child record. Is it by design?

I also found that, previously BO.Add() will call navigate() method which will also FilterChildRecords. However, it is remarked and replace with ForceNavigatedAndBoundRefresh() which doesn't filterchildrecords.



Please advice. Personally, I think Add() should auto filterchildrecords as well.



Thank you

Yes, by design.  If you look around the forum you will see that this has been a common topic in the past.  Generally from people having navigation issues because a filter is applied, a new record is added, and then the new record is not the current index.

The filter is respected on the add, but if you add a new record, you must set the columns that are part of the filter in order for the new record to show up where you expect it to be.  This is why we always recommend removing the filter prior to an add, set the columns that are part of the filter, then re-apply the filter.

Hi,

I still not get it. Shall you explain in more details?

If I manually call FilterChildRecords() after call Add(), would it cause any issue?



Thank you