dataApi and searchApi should implement ApiConfig interface that has the following properties:
Property Name
Type
Description
path
String
A path to API, for example: "data" or "search"
version
String
API Version, for example: "1.0" or "9.2"
Each API configuration will have a default path and version:
dataApi
{
path: "data",
version: "9.2"
}
searchApi
{
path: "search",
version: "1.0"
}
Default configuration values will allow developers to omit initialization of all configuration properties if not needed. For example:
new DynamicsWebApi({
serverUrl: "https://contoso.api.crm.dynamics.com/"
});
//requests to Data API will go to https://contoso.api.crm.dynamics.com/api/data/v9.2/
//requests to Search API will go to https://contoso.api.crm.dynamics.com/api/search/v1.0/
new DynamicsWebApi({
serverUrl: "https://contoso.api.crm.dynamics.com/",
dataApi: {
version: "9.1"
}
});
//requests to Data API will go to https://contoso.api.crm.dynamics.com/api/data/v9.1/
//requests to Search API will go to https://contoso.api.crm.dynamics.com/api/search/v1.0/
new DynamicsWebApi({
serverUrl: "https://contoso.api.crm.dynamics.com/",
searchApi: {
path: "future-search"
}
});
//requests to Data API will go to https://contoso.api.crm.dynamics.com/api/data/v9.2/
//requests to Search API will go to https://contoso.api.crm.dynamics.com/api/future-search/v1.0/
//and so on...
Configuration object for DynamicsWebApi needs to be rewritten to allow for configuration of Dataverse Search API.
webApiUrl
andwebApiVersion
must be removed and marked as deprecated in v1. #136The following properties should be added to a configuration object:
ApiConfig
data
.ApiConfig
search
String
dataApi
andsearchApi
should implementApiConfig
interface that has the following properties:String
String
Each API configuration will have a default
path
andversion
:dataApi
searchApi
Default configuration values will allow developers to omit initialization of all configuration properties if not needed. For example: