Skip to main content
Skip table of contents

Adding an AppData dSource

The steps to add a dSource in DCT, as outlined in the Linking wizard page, should be still be followed. However, this page covers details specific to adding an AppData dSource to DCT. AppData dSources allow for efficient handling and integration of application data.

Before initiating the linking process, ensure that an AppData type source is already added in DCT.

Steps effected during the Linking process

Data Source step

  1. Select AppData source: Initiate the dSource Linking wizard and select the desired AppData source. This selection is crucial in determining the linking procedure.

    image-20240121-195523.png
  2. Dynamic UI form: For an AppData database, a toolkit associated with it contains a linkedSourceDefinition. This definition, essentially a JSON schema, is rendered as a Dynamic UI form alongside the Source list. It outlines the necessary steps for linking sources of this type.

    • Direct AppData source: If selecting a direct AppData source, there’s an option for adding advanced settings, provided the linkedSourceDefinition has usesGrandfatheredAppDataProperties set to true.

      image-20240122-014853.png

Data Management step

  • This step is conditional and appears if:

    1. The source is a staged type.

    2. The source, whether direct or staged, requires snapshot parameter configuration.

  • Snapshot Parameters: These are determined by the toolkit’s snapshotParametersDefinition and are presented as a Dynamic UI form.

  • Staging Environment selection: Users can choose the appropriate staging environment and user credentials during this step.

image-20240122-015028.png

Completion

Continue through the linking process and after submission, the process of creating an AppData dSource begins. The new dSource will soon be visible on the dSource page, reflecting the configurations made during the linking process.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.