Hi all -



First use of the OverrideSearchTableName feature from the latest SF beta... a few questions popping up.



1.) It appears you must have all the columns that are in the "real" business object (i.e., the BO mapped to the actual SQL table that will be the target of inserts/updates) in the view? Makes sense, since the BD will then use its data to populate the real BO. Have I got this correct?



2.) Looks like you must always override the DataType if you want the Search Fields to use a "view-only" column, yes? Before doing this got strange-looking results where the view-only column was in the list of Search Fields, but the BD would not honor my checking it to include it in the list of fields I could use to enter selection criteria.



3.) Any differences in the implementation of this feature between the last beta and the current production release? In the process of renewing our license and I don't want to build stuff with the latest beta that will need reworking once I am on the latest production build.



TIA

________________
_____/ Regards,
____/ al

Movie Trivia Quote of the Day: "What we have here, is a failure to communicate."



I had been concerned that we were mixing Cowboys and Giants ) Thanks for the tip... the Company Name now appears in the BD's listivew... love it. Still have the "empty" DropDowns in the Search dialog for any search field that is a view-only (i.e., not part of the real BO), but I will try to not worry about that too much unless it creates a problem. (Maybe just a bit concerned as it seems to deviate from expected behavior).




________________
_____/ Regards,
____/ al

Have you downloaded 1.7.0.2 and then gone back into the editor to set the initial value? I fixed this in the most recent build to prevent this from happening.