Is your feature request related to a problem? Please describe.
Currently ODATA data source allows great way how to integrate with custom database solutions that implement ODATA standard.
When working with ODATA there may be however additional context needed for example when final URL is constructed on Server and there is need to take into consideration additional parameters that may not be added to ODATA URL.
Describe the solution you'd like
ODATA data source shall have current "properties" Dictionary exposed to user, so additional key/value pairs may be added and queried on server SDK. Currently there are Url and authentication properties already.
Describe alternatives you've considered
Serialize the additional data to Base64 and make them part of ODATA Url. This makes however URL large and is somewhat inflexible.
Is your feature request related to a problem? Please describe. Currently ODATA data source allows great way how to integrate with custom database solutions that implement ODATA standard.
When working with ODATA there may be however additional context needed for example when final URL is constructed on Server and there is need to take into consideration additional parameters that may not be added to ODATA URL.
Describe the solution you'd like ODATA data source shall have current "properties" Dictionary exposed to user, so additional key/value pairs may be added and queried on server SDK. Currently there are Url and authentication properties already.
Describe alternatives you've considered Serialize the additional data to Base64 and make them part of ODATA Url. This makes however URL large and is somewhat inflexible.
Additional context