Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik GA: Multivariate Time Series in Qlik Predict: Get Details
cancel
Showing results for 
Search instead for 
Did you mean: 
sriharinalam
Contributor
Contributor

Dynamic date filter expression in “filter conditions” box instead of “Record selection condition “

Required to write SQLite dynamic date filter expression in “filter conditions” box instead of “Record selection condition “ as shown below. (Because my source table has mandatory constraint of where clause)  

Labels (2)
1 Solution

Accepted Solutions
Heinvandenheuvel
Specialist III
Specialist III

For once I have to disagree with  @sureshkumar  and @john_wang .  

You just do not move that (any) column to the Filter Conditions. Instead use the RSE as you did. From the doc "Record Selection Condition: Enter a complex condition that can include multiple columns. The
condition must evaluate to TRUE to be accepted. You can create a condition using SQLite operators"

Filters executed on the source are only the 'passthru' filters and are only in effect during full-load, not apply-changes.

View solution in original post

3 Replies
sureshkumar
Support
Support

Hello @sriharinalam 

Dynamic values are not possible in filter condition

As in user guide its mentioned

"When the value in the selected column is equal to or more than the value you enter, the result is included or excluded in the replication task depending on the option selected in the Include/Exclude column"

Adding or removing filter ranges #Adding or removing filter ranges | Qlik Replicate Help

 

Regards,

Suresh

john_wang
Support
Support

Hi @sriharinalam ,

Totally agree with @sureshkumar . This is by design. The "Filter Conditions" has best performance (as the expression will be executed in source side database if possible) but it does not support complex expressions; The "Record Selection Condition" support complex expressions include dynamic input values however the performance is not as good as "Filter Conditions", because in latter filter mode, the rows will be retrieved from source DB, transferred to Replicate machine then being filtered in Replicate server, prior to apply to target side database. It may use more resources (CPU, and especially IO and network).

Hope this helps.

Regards,

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
Heinvandenheuvel
Specialist III
Specialist III

For once I have to disagree with  @sureshkumar  and @john_wang .  

You just do not move that (any) column to the Filter Conditions. Instead use the RSE as you did. From the doc "Record Selection Condition: Enter a complex condition that can include multiple columns. The
condition must evaluate to TRUE to be accepted. You can create a condition using SQLite operators"

Filters executed on the source are only the 'passthru' filters and are only in effect during full-load, not apply-changes.