Hi all,



Is it possible to specified or exclude the fields to be included in a BrowseDialog?



Since a Browse Dialog is assigned to a BO I believe that it will bring all fields in the BO, how to exclude a couple of fields in the SELECT statement so only the ones needed are used in the SELECT Field1, Field2, Field3, etc.?

Edhy Rijo

Hi Alex,



Based on my testing, you are wrong, the Browse Dialog will use all the fields in the BO as part of the SELECT statement.



When you create a BO and assign it to a BrowseDialog, all the fields in the BO will be use as part of the SELECT statement. In my case I have a Transactions table which have a couple of VARCHAR(MAX) and VARBINARY(MAX) fields, these are only used in a specific form, but the Transactions table is used in many forms, so when customer use a browse dialog, this process is slowed because those (MAX) fields are included in the main transactionsBO.



I am almost sure that the only way around this is using a View to define the specifics fields needed in most cases and then create a BO using this view. I just wanted to make sure there was no other way to avoid having to create the view and maintain it

Edhy Rijo

Aren't there some events you can use to manipulate the SQL being sent?

I looked at the Searching event, but it does handle the "WHERE" not the fields included or excluded from the BO.

Edhy Rijo

I'm not seeing anything either Edhy that would allow the fields included in the select to be manipulated.

Thanks Greg for the confirmation.



I am going with the View route and will do some testing soon, just that I need to do several changes since I want this to be used in all BDs.

Edhy Rijo

Ok here my conclusion, a view should be used and in this case of refactoring the source BO for the Browse Dialog it was worthy because in the BrowseResultLayout I need to show some calculated fields which I created using Custom Field Properties and those where also slowing things down a bit, so I decided to create my BrowserDialog view with a JOIN condition to get the calculated fields in a single trip and now getting and showing the data in the Browse Dialog is much faster and responsive.



One caveat to take into consideration using this approach is that after the user selects the record to work with from the BD, I them have to search that PK in the primary BO used in the form which in this case is not the one used in the BD. I know this can be confusing sometimes but in my case it works just fine because searching a record using the BO.FillByPrimaryKey(PKValue) is much faster than looking for many records in the BD which will include those VarBinary or Varchar fields that are not used in the BD.



Hey Alex, hope all this makes sense and if not, please let us know.

Edhy Rijo