<br><b>Code</b>: rsb:print<br><b>Error</b>: Formatter [ extable ] failed in the evaluation of <p> Microsoft Flow ?????????????????????????????????????????????[company_name] API Server ???[service] ADO.NET Provider ([x|db('v_drivers_count.total.count')]+ ???ADO.NET Providers) ?????Microsoft Flow ??????????????????API Server ??Microsoft Flow ?????????????[datasource] ?????OData ?Swagger ??????????????????????????Microsoft Flow ???????????[service] ????????? </p> <h2 id="setup">API Server ???????</h2> <p> Follow the steps below to begin producing secure and Swagger-enabled [service] APIs: </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>[service] ??????</h3> <p> After you deploy, provide authentication values and other connection properties by clicking Settings -> Connections 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> <p> You will also need to enable CORS and define the following sections on the Settings -> Server page. 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 specify the domains that are allowed to connect. <li><b>Access-Control-Allow-Methods</b>: Set this to a value of "GET,PUT,POST,OPTIONS". <li><b>Access-Control-Allow-Headers</b>: Set this to "x-ms-client-request-id, authorization, content-type". </ol> <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> For simplicity, we will allow the authtoken for API users to be passed in the URL. You will need to add a setting in the Application section of the settings.cfg file, located in the data directory. On Windows, this is the app_data subfolder in the application root. In the Java edition, the location of the data directory depends on your operation system: </p> <ol> <li>Windows: C:\ProgramData\\[company_name] <li>Unix or Mac OS X: ~/[company_name|tolower] </ol> <code> \[Application] AllowAuthtokenInURL = true </code> <h2>Add [service] [datatype] to a Flow</h2> <p> You can use the built-in HTTP + Swagger connector to use a wizard to design a [service] process flow: </p> <ol> <li>In Microsoft Flow, click My Flows -> Create from Blank. <li>Select the Recurrence action and select a time interval for sending emails. This article uses 1 day. <li>Add an HTTP + Swagger action by searching for Swagger. <li>Enter the URL to the Swagger metadata document: <code>https://MySite:MyPort/api.rsc/@MyAuthtoken/$swagger</code> <li>Select the "Return [extable]" operation. <li><p>Build the OData query to retrieve [datasource]. This article defines the following OData filter expression in the $filter box:</p> <p><var>[exselectwherecol] eq '[exselectwherecolequals]'</var></p> <p>See the API Server help documentation for more on filtering and examples of the supported OData.</p> </ol> <img src="[x|UrlRootAbs]/kb/articles/odata-microsoft-flow-1.png" title="The wizard to build the OData query. (Salesforce is shown.)"/> <h2>Trigger an Action</h2> <p> You can now work with [extable] entities in your process flow. Follow the steps to send an automated email: </p> <ol> <li>Add an SMTP - Send Email action. <li>Enter the address and credentials for the SMTP server and name the connection. Be sure to enable encryption if supported by your server. <li>Enter the message headers and body. You can add [service] columns in these boxes. <img src="[x|UrlRootAbs]/kb/articles/odata-microsoft-flow-2.png" title="An email to be populated with results from an OData query. (Salesforce is shown.)"/> </ol>. 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-microsoft-flow.rst