1.) Change the search record on the component to your desired Search Record.

2.) Open the CI definition and look for any red "x"s over the properties on the right hand side. Delete those as needed. This could potentially break other pieces of code using this CI so be sure to do your research on where this is used and if possible use the same properties names on the new search record properties to minimize the impacts.

3.) On all menus where that component is placed, put a menu level search record override back to the original with row level security search record.

The end result is that the code calling the CI will result in your desired behavior (NO RLS) but any online web users will still have the row level security functionality.

Shameless plug. This and a bunch of other topics on ci are covered in my CI training video over at my website. www.cedarhillsgroup.com

I am wondering how to override a component's Add Search Record when running a component interface?

I have a component interface built on the Positive Input component where an Add Search Record is in place which is a view with security (row class security) enforced. When this CI is triggered, I would like this view to be substitute or override with another view which does not have security applied. The whole idea is that when adding a new PI row online, the row calss security should be kicked off by using the view with the security but when the CI is triggered teh security should be bypassed by using a different view without security.

Has anyone done on this before? Your help is much appreciated.

Thanks.