[Blama]

Hi Isomorphic,

What do you mean by "the tag is supported"? What tag?

The DataSource.implicitCriteria tag. It's not in the .ds.xml docs (as of today) and then should be at #implicitCriteria.

OperationBinding.criteria is for a specific operationBinding and DataSource.implicitCriteria affects all fetches.

DataSource.implicitCriteria is only applied for client requests, as it is a declarative security feature (see #11).
Question was if this also applies to DataSource.implicitCriteria or can this be used to e.g. always for all requests filter e.g. deleted='Y' rows.

Best regards
Blama

[Isomorphic]

Please re-read your last two sentences - there's a thinko in there somewhere as you repeated DataSource.implicitCriteria twice but we think you actually meant to contrast it with something else.

[Blama]

Hi Isomorpic

yes, mixup. It should read:

OperationBinding.criteria is only applied for client requests, as it is a declarative security feature (see #11).
Question was if this also applies to DataSource.implicitCriteria or can this be used to e.g. always for all requests filter e.g. deleted='Y' rows.

Best regards
Blama

[claudiobosticco]

This has now been fixed - you can test out the change in builds dated April 11.

For clarity, case doesn't matter because advancedCriteria.criteria / criterion.criteria is a multiple="true" field, and we're using the uniform format for such fields.

I can confirm that it's working for me.

[Isomorphic]

Re: #18, DataSource.implicitCriteria is an entirely client-side feature, it is added by client-side components. So it does not affect server-side requests, and will not be added to client-side requests that don't come from a SmartClient UI (eg RestHandler). This clarification will be added to the docs soon.