# Configuring Infor M3 REST connector

* In the **Novacura Flow Studio**, under the **Environment** tab, you will find **Connectors**. Click on it and press **Add** to create a new record. 

<figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FlldTNeU99cxz6EnPo1cX%2Fimage5.png?alt=media&#x26;token=16ca0d1e-c863-4d96-abdf-d284c6278180" alt=""><figcaption><p>Adding a new connector</p></figcaption></figure>

* Provide a **Name** and choose the **Infor M3 REST API** from the **Type** drop-down. Drill down the **Configuration** and provide the API Endpoint **URL** as well as tenant/M3 in **Additional Path** to indicate the Infor M3 CloudSuite environment. \
  Example: \
  URL: <https://mingle-ionapi.eu1.inforcloudsuite.com\\>
  Additional Path: Tenantexample\_TST/M3
* Define **Force style for errors**. The default option will be Empty Record. By setting **Force style for errors**, you can dictate how an error response from Infor M3 REST should be interpreted in Flow.

  * Empty Record - Flow will return an empty record in case of an error message returned from Infor M3.&#x20;
  * Nil Record - Flow will return a Nil record in case of an error message returned from Infor M3.

  <figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FgCbg5LD4fUZ9BzISXOHC%2Fimage.png?alt=media&#x26;token=9c413309-9c8a-4a8b-b099-1272e02ddbc1" alt="" width="557"><figcaption><p>Connector Settings</p></figcaption></figure>

{% hint style="info" %}
**Force style for errors** option is only available starting from Flow Studio version [6.15.10](https://help.novacuraflow.com/release-information/flow/6.15/studio/6.15.10) & Flow service pack [6.15.12](https://help.novacuraflow.com/release-information/flow/6.15/server/6.15.12)
{% endhint %}

* Click on **Setup auth**. Tick on **Use OAuth2** and **Load from ionapi-file** to fetch all the editable credentials automatically via the downloaded file. Repeat the same procedure on **Runtime** tab.

<figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FJaUj4sXEpJSvy515f052%2Fimage6.png?alt=media&#x26;token=20d3f44e-6d14-4c8a-857a-cdb50e5d761a" alt=""><figcaption><p>Edditing Token details</p></figcaption></figure>

* Under **Advanced** tab, specify if the invoked API will be personal. In other words, you can either create a Novacura Flow User Id as M3 User ID or assign a property to a Novacura Flow User Id which value will correspond to a M3 User Id.\
  \
  That function only works when either '**GRID-Administrator**' or '**GRID-RunAsM3User**' IFS (Infor Federation Services) Security Role is assigned to a M3 User ID used as Service Account!

<figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2Fab24xI4jCZzkdPOAj8MB%2Fimage7.png?alt=media&#x26;token=f49e8aa4-aadd-4f3f-bc55-169cd4649fa6" alt=""><figcaption></figcaption></figure>

* After the credentials are successfully imported, click **Save** and then **Save** again on the Connector to save the changes. You should be able now to use the connector!&#x20;