Unexpected results when shifting to Nightly Version

udaymagdum

We moved from DataTables 1.1.0 to 1.3.0 to address the multiple calls issue in 1.1.0. Thank you.

We've noticed two things:
1. The 'Equals' condition now works with a single line input control where the user must type a value, instead of picking their value from a dynamic select list - Is that by design or a defect?
For the 'Equals' condition: Is there option to indicate by attribute, when to render a select list or a single line input? This would be ideal.
2. Date attribute types now include time and time zone; the type of 'date' was not being passed to the server, and now a type is being passed of 'moment', resulting is a DataTable warning. Is there an option to not pass the type?

Are there any other known issues with this upgrade that we should be aware of; do you have a prelim release note or equivalent that we can review?

colin

I'm not seeing either of those things here with the standard example.

We're happy to take a look, but as per the forum rules, please link to a test case - a test case that replicates the issue will ensure you'll get a quick and accurate response. Information on how to create a test case (if you aren't able to link to the page you are working on) is available here.

Cheers,

Colin

udaymagdum

@colin

Sorry I made mistake while posting question.

This Question regarding SearchBuilder

We moved from SearchBuilder version 1.1.0 to 1.3.0(Nightly Builde version) to address the multiple calls issue in 1.1.0.

1. we observed Above mentioned things where we use server side implementation for data table.

2. In case of client Side implemention of data table above mentioned things not happens(As you given reference link https://datatables.net/extensions/searchbuilder/examples/initialisation/simple.html).

As attached screenshot you see value field select list changed with input field.

kthorngren

You will want to review the SearchBuilder Server Side Processing docs support. Support for SSP was added n 1.2.0.

Also there is this:

There are two caveats that SearchBuilder's server-side integration carries. The first is that anywhere select elements would normally be used on the client-side, input elements are used instead.

Sounds like the behavior you are seeing is expected.

Kevin