By default, multi-selection for intent-based navigation is enabled.
This topic is only applicable to SAP Fiori elements for OData V4.
The records that do not have a unique key field cannot be identified. For example, if the following contexts are to be passed during navigation:
Record
P1
P2
1
A
X
2
B
Y
3
A
Y
The navigation context that is passed has (P1=A or B) and (P2=X or Y) rather than (P1=A and P2=X) and (P1=B and P2=Y) and (P1=A and P2=Y). In the target app, individual properties are concatenated using AND, and multiple property values are concatenated using OR: (P1=A OR P1=B) AND (P2=X OR P2=Y). This might result in an additional record BX.
The selection variant that is passed has the following format:
Structure of the selection variant that is passed
{"selectionVariant": "SelectOptions":[ {"PropertyName":"SalesOrder","Ranges":[ {"Sign":"I","Option":"EQ","Low":"2919682","High":null}, // Context from 1st record for "SalesOrder" {"Sign":"I","Option":"EQ","Low":"2915717","High":null} // Context from 2nd record for "SalesOrder" ]}, {"PropertyName":"SalesOrderType","Ranges":[ {"Sign":"I","Option":"EQ","Low":"OR","High":null}, // Context from 1st record for "SalesOrderType" {"Sign":"I","Option":"EQ","Low":"SE","High":null} // Context from 2nd record for "SalesOrderType" ]}, {"PropertyName":"TransactionCurrency","Ranges":[ {"Sign":"I","Option":"EQ","Low":"EUR","High":null}, {"Sign":"I","Option":"EQ","Low":"USD","High":null} ]}, ..... .....