Hi, In general, the use of a subscription mode when subscribing to an item involves two components:
- On the client side, the subscription request must specify the mode.
- On the server side, the Metadata Adapter must allow the mode for that item.
I suppose that the latter is the missing step.
In general, the Metadata Adapter gives allowance to a mode through two callbacks: modeMayBeAllowed and isModeAllowed.
As far as the Basic Demo is concerned, you don't need to modify the Metadata Adapter, but only its configuration, which is in the adapters.xml file.
You should find lines like the following:
<param name="item_family_1">item.*</param>
<param name="modes_for_item_family_1">MERGE</param>
and you can specify the desired mode (i.e. DISTINCT) there.
Note that this will take effect for all items; if the change should regard one item only, a fine-tuning of this configuration would be needed.
Consider that using a mode for an item is not a free choice, because each mode may put restrictions on the updates that the Data Adapter should provide.
In this case, you shouldn't have any problem; but, for instance, you cannot set COMMAND, where the updates are supposed to provide the special "key" and "command" fields.
