If you have a support call open, would help if you reference that in your posts.

You did not provide any examples of expressions you say are of concern.

Queries that reference datasets will execute in the Compute Service which supports many of the temporal expressions.

- Date Calculation field is: cast( End_Date - Start_Date ; interval second). But same issue occur with _unix_timestamp ( End_Date ) . I need difference between these two timestamps in seconds.

When adding all those fields to a report, you will see that query is split and join is done by Query Service, not Compute Service.

If you have a support call open, would help if you reference that in your posts.

You did not provide any examples of expressions you say are of concern.

Queries that reference datasets will execute in the Compute Service which supports many of the temporal expressions.

The interval type is not supported with data sets.

Use _seconds_between ( ) expression instead of type casting to an interval type

https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=administration-queries-uploaded-files-data-sets

- Date Calculation field is: cast( End_Date - Start_Date ; interval second). But same issue occur with _unix_timestamp ( End_Date ) . I need difference between these two timestamps in seconds.

When adding all those fields to a report, you will see that query is split and join is done by Query Service, not Compute Service.

If you have a support call open, would help if you reference that in your posts.

You did not provide any examples of expressions you say are of concern.

Queries that reference datasets will execute in the Compute Service which supports many of the temporal expressions.

Hi Nigel,

Thanks for your help. Function _seconds_between(  ) works when the two fields are from dataset.

But, if I try _seconds_between( current_timestamp ; Start_Date ), local processing is done.

The data module made by an user is doing exactly this, using current_timestamp.

Is there a way to avoid local processing calculating with current_timestamp?

Do you know if there is a configuration that can block/deny local processing of queries? We have 1,000 users and we do not have control that is created/developed by them.

The interval type is not supported with data sets.

Use _seconds_between ( ) expression instead of type casting to an interval type

https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=administration-queries-uploaded-files-data-sets

- Date Calculation field is: cast( End_Date - Start_Date ; interval second). But same issue occur with _unix_timestamp ( End_Date ) . I need difference between these two timestamps in seconds.

When adding all those fields to a report, you will see that query is split and join is done by Query Service, not Compute Service.

If you have a support call open, would help if you reference that in your posts.

You did not provide any examples of expressions you say are of concern.

Queries that reference datasets will execute in the Compute Service which supports many of the temporal expressions.

Hi Nigel,

Thanks for your help. Function _seconds_between(  ) works when the two fields are from dataset.

But, if I try _seconds_between( current_timestamp ; Start_Date ), local processing is done.

The data module made by an user is doing exactly this, using current_timestamp.

Is there a way to avoid local processing calculating with current_timestamp?

Do you know if there is a configuration that can block/deny local processing of queries? We have 1,000 users and we do not have control that is created/developed by them.

The interval type is not supported with data sets.

Use _seconds_between ( ) expression instead of type casting to an interval type

https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=administration-queries-uploaded-files-data-sets

- Date Calculation field is: cast( End_Date - Start_Date ; interval second). But same issue occur with _unix_timestamp ( End_Date ) . I need difference between these two timestamps in seconds.

When adding all those fields to a report, you will see that query is split and join is done by Query Service, not Compute Service.

If you have a support call open, would help if you reference that in your posts.

You did not provide any examples of expressions you say are of concern.

Queries that reference datasets will execute in the Compute Service which supports many of the temporal expressions.

Hi Nigel,

Thanks for your help. Function _seconds_between(  ) works when the two fields are from dataset.

But, if I try _seconds_between( current_timestamp ; Start_Date ), local processing is done.

The data module made by an user is doing exactly this, using current_timestamp.

Is there a way to avoid local processing calculating with current_timestamp?

Do you know if there is a configuration that can block/deny local processing of queries? We have 1,000 users and we do not have control that is created/developed by them.

The interval type is not supported with data sets.

Use _seconds_between ( ) expression instead of type casting to an interval type

https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=administration-queries-uploaded-files-data-sets

- Date Calculation field is: cast( End_Date - Start_Date ; interval second). But same issue occur with _unix_timestamp ( End_Date ) . I need difference between these two timestamps in seconds.

When adding all those fields to a report, you will see that query is split and join is done by Query Service, not Compute Service.

If you have a support call open, would help if you reference that in your posts.

You did not provide any examples of expressions you say are of concern.

Queries that reference datasets will execute in the Compute Service which supports many of the temporal expressions.

use localtimestamp 

Hi Nigel,

Thanks for your help. Function _seconds_between(  ) works when the two fields are from dataset.

But, if I try _seconds_between( current_timestamp ; Start_Date ), local processing is done.

The data module made by an user is doing exactly this, using current_timestamp.

Is there a way to avoid local processing calculating with current_timestamp?

Do you know if there is a configuration that can block/deny local processing of queries? We have 1,000 users and we do not have control that is created/developed by them.

The interval type is not supported with data sets.

Use _seconds_between ( ) expression instead of type casting to an interval type

https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=administration-queries-uploaded-files-data-sets

- Date Calculation field is: cast( End_Date - Start_Date ; interval second). But same issue occur with _unix_timestamp ( End_Date ) . I need difference between these two timestamps in seconds.

When adding all those fields to a report, you will see that query is split and join is done by Query Service, not Compute Service.

If you have a support call open, would help if you reference that in your posts.

You did not provide any examples of expressions you say are of concern.

Queries that reference datasets will execute in the Compute Service which supports many of the temporal expressions.