HTML5 Data Bindings Support Product Page

Solved

Filter As You Type Issue

Reported 16 Jan 2015 20:07:42
2
have this problem
16 Jan 2015 20:07:42 DuFour DuFour posted:
With the old data source connecting code, Filter As You Type worked fine:
{"id": "dsNews", "url": "../../../dmxDatabaseSources/dsnNews.php?filter={{$FORM.filter}}&limit=", "dataSourceType": "database", "dataType": "jsonp"}
);

However, now with the updated version, it doesn't work:
{"id": "dsNews", "url": "../../../dmxDatabaseSources/dsnNews.php", "data": {"filter": "{{$FORM.filter}}", "limit": ""}, "dataSourceType": "database", "dataType": "jsonp"}
);

If I make an update to the data source, the updated code will override any changes I may have made, so then Filter As You Type doesn't work.

Replies

Replied 11 Apr 2016 05:30:19
11 Apr 2016 05:30:19 Greta Garberini replied:
I was told that the new version is working exactly as the old one, only some algorithms have been moved to the action files system. If I refer to this video: www.youtube.com/watch?v=Q8HNY6NWZDg (filter as you type)
I wonder how I can achieve this?
I would like to use it in combination with the latest "HTML5 Data Bindings State Management". It is nice to have the pagination state stored but to browse through hundreds of records without a search function is almost useless.
Replied 11 Apr 2016 06:44:12
11 Apr 2016 06:44:12 Teodor Kuduschiev replied:
Hello Greta,
What exactly the filter as you type is?
Nothing has changed with it, since the release of the server connect - it is the same.
Replied 11 Apr 2016 07:04:53
11 Apr 2016 07:04:53 Greta Garberini replied:
I simply don't succeed to apply it. I guess as a developer you mean what you say when stating "Nothing has changed". To me as a client, there has been a lot of changes. I simply can't translate the content of this video tutorial to the new Data Bindings State management to combine the two extensions. The paged query works fine. Can you give a hint how to apply the "filter as you type" action to it?
Replied 11 Apr 2016 07:07:10
11 Apr 2016 07:07:10 Teodor Kuduschiev replied:
It is the same way as with data bindings ...
1. You create a query with a form filter
2. You place the filter as you type code on the page
Replied 11 Apr 2016 07:10:07
11 Apr 2016 07:10:07 Greta Garberini replied:
OK, do you mean to create an extra query? I tried to use the filter in the "Paged Query".
Replied 11 Apr 2016 07:17:56
11 Apr 2016 07:17:56 Teodor Kuduschiev replied:
Use your current query .... just add filter to it.
Replied 11 Apr 2016 08:18:35
11 Apr 2016 08:18:35 Greta Garberini replied:
OK, that's what I did earlier: I added this to my filter's list, added (by clicking)
{{$_POST.listensuche}}
, while "listensuche" being the name and id of the search field. I had to add the same condition in the action file, otherwise it would not display any data at all. (BTW the paged query properties keep losing the entered limit and resets its values to the default setting).
Then I clicked the search form field and added
onKeyUp="MM_callJS('$.dmxDataBindings.globalScope.update(\'$FORM\');')"

as a behavior to the form field.

It simply does not work, no matter what I enter in the search field.
Replied 11 Apr 2016 08:25:07
11 Apr 2016 08:25:07 Teodor Kuduschiev replied:
And did you bind the {{$_POST.listensuche}} to the form field in the executor, checking the "Refresh data on change" checkbox?
Replied 11 Apr 2016 08:34:38
11 Apr 2016 08:34:38 Greta Garberini replied:
Shoot, I really had forgotten the checkbox "Refresh data on change", but unfortunately it did not change the outcome. The filter still does not work.
Replied 11 Apr 2016 08:37:44
11 Apr 2016 08:37:44 Teodor Kuduschiev replied:
Please provide a link to your page.
Replied 11 Apr 2016 08:42:36
11 Apr 2016 08:42:36 Greta Garberini replied:
I sent the link via email to
Replied 11 Apr 2016 12:29:32
11 Apr 2016 12:29:32 Greta Garberini replied:
There was an old supporting file, causing the error. Thanks to Teodor this could be resolved.

Reply to this topic