<br><b>Code</b>: rsb:print<br><b>Error</b>: Formatter [ extable ] failed in the evaluation of <p> Microsoft PowerApps ????????????????????????????????&??????????????????[company_name] API Server?ADO.NET Provider for [service] (????[x|db('v_drivers_count.total.count')]+ ???ADO.NET Providers) ??????????PowerApps ??????????????????????????????PowerApps ?Common Data Service ?????????????????????[company_name] API Server ??[service] ????????????????????????SaaS API ?NoSQL ???????SQL-92 ????????????????? </p> <p> [company_name] API Server ?Swagger ?????????????????Azure App Service?Microsoft Flow????PowerApps ?Swagger ????????UI ??????????????Swagger ???????PowerApps ??[service] ????????????????????????????PowerApps ???????????[datasource] ?????????????? </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 by clicking Settings -> Connections and adding a new connection in the API Server administration console. You can then choose the entities you want to allow the API Server access to by clicking Settings -> Resources. [extraconnectionnotescloud|def('[extraconnectionnotes|def("")]')] </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> You will also need to enable CORS and then define the following sections by clicking Settings -> Server. As an alternative, you can select the option to allow all domains without '*'. </p> <ol> <li><b>Access-Control-Allow-Origin</b>: Set this to a value of '*', or the domains you will be calling the API Server from. <li><b>Access-Control-Allow-Methods</b>: Set this to a value of "GET,PUT,POST,OPTIONS", or the HTTP methods you will need to use. <li><b>Access-Control-Allow-Headers</b>: Set this to "x-ms-client-request-id, authorization, content-type". </ol> <p> Last, you will need to configure the API Server to allow users to authenticate by passing the authtoken as a part of the URL. To do so, navigate to the www/app_data folder in the installation direction and modify the settings.cfg file to add the following line in the <var>\[Application]</var> section: </p> <code> AllowAuthTokenInURL = true </code> <h2>Retrieve the Swagger Metadata</h2> <p> You will use the metadata to create a Custom API connection. You can obtain the Swagger definition by making the following request in your browser and then saving the resulting JSON file:</p> <code>http://MySite:MyPort/api.rsc/$swagger</code> <h2>Connect to [service] Through the API Server</h2> <p> The following procedure shows how to create a simple app that searches remote [datasource]. </p> <ol> <li>In Microsoft PowerApps, click Custom connectors. <li>Click Create customer connector and choose Import an OpenAPI file. <li>Name the connector, browse to the JSON file, and click Continue. <li>Fill in the relevant General information, ensure that Base URL is of the form <var>/api.rsc/@myauthtoken</var> (where <var>myauthtoken</var> is the AuthToken for a configure API Server user), and click Continue. <li>Select Basic authentication for the Authentication type and use the default Parameter labels and names. Click Continue. <li>Review the Action and Reference definitions and click Create connector. <li>To test the connector, you will need to create a new connection. Click Test, click New Connection under Connections, and click Create. <li>Navigate back to the connector from the Custom connectors menu and click Test. From here, you can test the available operations. </ol> <h2>Connect the Data Source to a PowerApp</h2> <p> Follow the steps below to connect to [service] from a PowerApp:</p> <ol> <li>From the PowerApps main menu, click Create an app and select the on-premises or cloud PowerApp Studio. <li>Select a blank app (choose Phone layout or Tablet layout). <li>In the View tab, click Data Sources and click Add data source. <li>Click the Connection you created to test the connector. </ol> <h2>Populate a Gallery</h2> <p> Follow the steps below to create a simple app that can search [datasource]. You will use PowerApps formulas to bind [service] rows to rows in a gallery control. </p> <ol> <li><p>In the View tab, click Gallery -> Vertical to add a Gallery. </p> <li> <p> After selecting a gallery, assign the Items property of the gallery to [datasource] on the Advanced tab of the gallery settings. The formula below will allow you to access columns in the [extable] table. </p> <code>ForAll([company_name]SwaggerAPI.getAll[extable|capitalize]().value, {my[excol#1]: [excol#1], my[excol#2]: [excol#2]})</code> <li> <p> Assign [service] columns to UI elements by clicking the element and then setting the Text property (on the Advanced tab of the UI element) to <var>ThisItem.my[excol#1]</var> or <var>ThisItem.my[excol#2]</var>. </p> <img src="[x|UrlRootAbs]/kb/articles/odata-powerapps-1.png" title="Adding the connection to the layout."/> </ol> <h2>Search [service] [datatype]</h2> <p> To filter the records displayed by the gallery, add a TextInput to your Screen, clear the Text property for the TextInput, and set the Items property of the gallery to a formula like the one below, replacing <var>TextInput1</var> with the name of the TextInput control in your gallery, if necessary: </p> <code>If(IsBlank(TextInput1.Text), ForAll([company_name]SwaggerAPI.getAll[extable|capitalize]().value, {my[excol#1]: [excol#1], my[excol#2]: [excol#2]}), ForAll([company_name]SwaggerAPI.getAll[extable|capitalize]({'$filter':Concatenate("contains([excol#1],",TextInput1.Text,")")}).value, {my[excol#1]: [excol#1], my[excol#2]: [excol#2]}))</code> <p> The formula builds an OData query that the API Server executes against the remote [datasource], ensuring that the search is run against the current data without first pulling in every record into the app. You can find more information on the supported OData in the API Server help documentation. </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/ponparemall-odata-powerapps.rst