<br><b>Code</b>: rsb:print<br><b>Error</b>: Formatter [ extable ] failed in the evaluation of <p> ??????[company_name] API Server ?ADO.NET Provider for [service] (????[x|db('v_drivers_count.total.count')]+ ???ADO.NET Providers) ?????????????????DB ????????????[service] API ???????????SAPUI5 ???????????API Server ??[datasource] ?OData ???????????????????????OData ?SAPUI5 ???OpenUI5 ???????????? </p> <h2 id="setup">Set Up the API Server</h2> <p> Follow the steps below to begin producing secure [service] OData services: </p> <h3>Deploy</h3> <p> The API Server runs on your own server. On Windows, you can deploy using the stand-alone server or IIS. On a Java servlet container, drop in the API Server WAR file. See the help documentation for more information and how-tos. </p> <p> The API Server is also easy to deploy on <a href="[x|UrlRootAbs]/kb/articles/odata-azure.rst">Microsoft Azure</a>, <a href="[x|UrlRootAbs]/kb/articles/odata-amazon.rst">Amazon EC2</a>, and <a href="[x|UrlRootAbs]/kb/articles/odata-heroku.rst">Heroku</a>. </p> <h3>Connect to [service]</h3> <p> After you deploy the API Server and the <a href="[x|UrlRootAbs]/drivers/[id]/download/ado">ADO.NET Provider for [service]</a>, provide authentication values and other connection properties needed to connect to [service] by clicking Settings -> Connections and adding a new connection in the API Server administration console. </p> [extraconnectionnotescloud|def('[extraconnectionnotes|def("")]')] <p> You can then choose the [service] entities you want to allow the API Server access to by clicking Settings -> Resources. This article uses [extable] as an example. </p> <h3>Authorize API Server Users</h3> <p> After determining the OData services you want to produce, authorize users by clicking Settings -> Users. The API Server uses authtoken-based authentication and supports the major authentication schemes. You can authenticate as well as encrypt connections with SSL. Access can also be restricted by IP address; Access is restricted to only the local machine by default. </p> <p> <h2>Create the View</h2> <p> In this article the user views and interacts with [datasource] through an SAPUI5 table control. Table columns will be automatically detected from the metadata retrieved from the API Server's API endpoint. We define the following table in a separate View.view.xml file: </p>. The error was: The value of the attribute could not be accessed: The attribute does not exist.<br><b>URL</b>: /jp/kb/tech/veevacrm-odata-sapui5.rst