The OnBase Feature Layers for Esri REST API contains the following limitations:
-
Esri web maps have limited functionality when used with Esri Portal Online or Portal On-Premise. Filter support is limited and table display of features is unsupported. It is recommended to use Esri web maps with Esri Portal Online or Portal On-Premise for aggregate views or document links.
-
Some contains clauses in Query operations are not supported and can depend on wildcard settings for OnBase Keyword Types.
-
Document Dates must be searched for using a where clause in the Query operation.
-
The Find operation is only supported for use with Keyword Types. It is not supported for use with the OnBase Document Date.
-
Although caching is enabled on a per-server basis for requests for REST queries across clients, requests for many different queries can negatively impact performance. It is recommended to limit the number of queries made per client as much as possible.
-
Only JSON data is returned along with the formatted JSON object if an output format of JSON is requested (f=pjson).
-
When querying OnBase Feature Layers with the Esri Query Tool, only numeric values can be queried on.
-
As of OnBase Foundation 22.1, using the default Esri geocoders with the OnBase Feature Layers for Esri REST API is no longer supported. Documents that were geocoded by these geocoders in a previous version can still be displayed using OnBase Feature Layers for Esri REST API, but if any of the address Keyword Values of those document are updated, the document will no longer be displayed on the map.