LinkedIn
Copied!

Table of Contents

Updating connections and field mappings for a data source

Version:

Only available versions of this content are shown in the dropdown

To keep connection details current, reconnect data views to a data source when connection details have changed. You can update existing connection details and field mappings, for example, if the authentication method has changed, or the schema of the data being sent has changed.

In general, only data sources created in App Studio can be updated in App Studio; however, there are conditions when a data source created in App Studio cannot be updated. In these cases, only the replace option is available. The update option is not available for data sources created in App Studio when:

  • The JSON data transform or connector is opened and saved in Dev Studio.
  • The normal response data transform is modified in Dev Studio so that it no longer references only one updatable JSON data transform.
  • The data page is modified in Dev Studio in any of the following ways:
    • The data page no longer references a normal data transform as the response data transform.
    • The data page references a request data transform.
    • The connector parameters for the data source are obtained from the current parameter page (Pass current parameter page is set to true).

Data sources created in Dev Studio can only be updated in Dev Studio.

  1. In the navigation pane of App Studio, click Data.

  2. Click Data objects and integrations.

  3. Click a data object.

  4. Click the Data views tab.

  5. On the Data views tab, in the row of the data view that you want to configure, click More Update source .

  6. In the Connection details section, in the Method field, select the connection method, GET or POST.

  7. In the Endpoint URL field, enter the endpoint URL of the data.

  8. In the Parameters section, choose which part of the URL are dynamic and need to be parameterized for future calls.

    1. Select the URL part that you want to parameterize.

    2. In the Parameter name field, enter the name.

  9. In the Headers section, click Add header to specify a request header and its value. Some services require extra information, for example, API version.

  10. In the Authentication section, select the type of authentication to use to connect to the system of record.

  11. Click Next.

  12. Optional:

    Update the data mapping as needed.

  13. Click Next.

  14. Optional:

    In the section for the environment that you are configuring, in the Endpoint URL field, enter the endpoint URL of an external system.

  15. Optional:

    Configure authentication for the endpoint, based on the type of authentication that you choose.

    • To not authenticate, in the Authentication mode field, select None.
    • To use the basic HTTP authentication credentials:
      1. In the Authentication mode field, select Basic.
      2. In the User name field, enter a valid user name.
      3. Click Set password.
      4. Enter a password for the user name that you entered.
      5. Click Submit.
      6. In the Realm field, enter the realm of the user account on the server to which you are connecting.
      7. In the Host name field, enter the host name of the server to which the request is being sent.
      8. Optional: To receive a basic authentication request before the server gives an unauthorized response, select Preemptive authentication. Selecting this check box reduces connection overhead.
    • To use the NT LAN Manager credentials:
      1. In the Authentication mode field, select NTLM.
      2. In the User name field, enter a valid user name.
      3. Click Set password.
      4. Enter a valid password for the user name that you entered.
      5. Click Submit.
      6. In the Domain field, enter the domain of the user account that you provide in the User name field.
      7. In the Host Name field, enter the host name of the server to which the request is being sent.
  16. Optional:

    Repeat steps 14 and 15 for each environment you are configuring.

  17. Click Submit.

When you update a data source:

  • Previously generated artifacts are not deleted. New artifacts are created.
  • A new authentication profile is created if authentication is configured.
  • The REST connector and JSON data transform are versioned.
  • The response data transform (non-JSON) and integration class are not modified.
  • The data page is versioned if you make any changes to parameters on the Request tab of the visual mapper; otherwise, the data page is not modified.
Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.