Search and Sort on the same recordset

Hi WA,

Can I apply a search AND sort on the same Recordset on the same page?

I have a results page and want to be able to use the WA extensions to

a) Sort if applicable
b) Filter by a category

Thanks
Ian

Ys, you can use the DataAssist Search and Sort behaviors on the same page.

Thanks Jason,

I've managed to get it working now. For some reason each time I apply Data Assist Sort it butchers my recordset, taking the Data Type of the Parameters section.

I can add it back manually and everything works OK, until I need to go in and make changes to the Sort Behaviour.

However all working for now!

Cheers
Ian

I have not run into that problem before.


can you send a copy of the page before editing the sort and another copy of the page after editing the sort so i can see what it is doing to the code, also provide details on your DW version and OS please.

I also have this problem and since there was no response, here is the code for my problem. DW CS4 on Vista.

Before applying DASearch
, GetSQLValueString($Paramadmin_WADAct_application, "int"),GetSQLValueString($Parambranch_WADAct_application, "int"),GetSQLValueString($Paramidbranch_WADAct_application, "int"),GetSQLValueString($Paramteacher_WADAct_application, "int"),GetSQLValueString($Paramidteacher_WADAct_application, "int"));

After applying DA Search
, GetSQLValueString($Paramadmin_WADAct_application,"int"),GetSQLValueString($Parambranch_WADAct_application,"int"),GetSQLValueString($Paramidbranch_WADAct_application,"int"),GetSQLValueString($Paramteacher_WADAct_application,"int"),GetSQLValueString($Paramidteacher_WADAct_application);

A red exclamation point also appears next to the Recordset in the Server Behaviors panel. I must add both the space between the comma and the "int" for each parameter and the data type for the last parameter.

Hope this helps.

OK, I see now. the issue is not so much caused by using DataAssist search and sort at the same time, it is applying sort to a recordset that contains parameters.


Thank you for clarifying this.

I have logged the issue in our bugbase.