How To Set Up Spider Samples

The features that are available as ready-made examples for Spider can be installed and set up, for example, for a demo or training purpose.

Import G/L Entries

There is a "sample extension" for importing general ledger entries via the Integration Queue which can be set to mimic a scenario where a general ledger file shall be imported and handled in a structured and controllable manner and it shall be possible to achieve tracking between the system that delivers the file and Business Central.

Step 1: Upload And Deploy Extension

Upload the Per-Tenant Extension (PTE).

Note

Find the source code of the Spider samples on GitHub.

Step 2: Create Integration

  1. Choose the search icon (ALT+Q), enter Integrations, and then choose the related link.
  2. Select New.
  3. Enter a Code.
  4. Select Import G/L Entries in the Integration Type field.
  5. Select the Additional Settings action.
    1. Select a Posting Nos. and a Source Code.
  6. Select an existing Communication Method or create a new.
Tip

We recommend that you choose a unique Source Code for this integration to enable better tracking capabilities.

Note

You can choose to activate the Skip Dupe Check toggle to enable that the same file can be imported multiple times (which can be useful for demo or educational purposes).

Step 3: Create Communication Method

  1. Choose the search icon (ALT+Q), enter Communication Method, and then choose the related link.
  2. Select New.
  3. Enter a Code.
  4. Select the appropriate Type depending on where the sample file (to import) is/should be stored.
  5. Select the Edit action.
  6. Hover over a field to read a short description and proceed to fill the fields as necessary.

Step 4: Handle File in the Integration Queue

  1. Choose the search icon (ALT+Q), enter Integration Queue, and then choose the related link.
  2. Hover over a field or action to read a short description.
  3. Select the Import action to retrieve the file.
  4. Select the Execute Line One Step action to parse the file.
  5. Select the Details action to view the contents of the file.
  6. Select the Execute Line One Step action to validate the file.
  7. Select the Execute Line One Step action to post the file.
  8. Select the Execute Line One Step action to archive the file.
Note

It is only for demo and educational purposes that a file is handled one step at a time. Otherwise all steps are handled simultaneously with the Import and Execute All Lines action.

Tip

It is possible to edit the contents of the file after selecting the Details action. All changes made are marked in the Manually Changed checkbox field.

Note

The file is the example file stored in the location specified for the communication method linked to the integration.

Find Handled Entries

  1. Choose the search icon (ALT+Q), enter Integration Queue History, and then choose the related link.
  2. You will find all information related to the posted file. You can see information about the original file, if something has been manually changed, and the transactions that have been posted.

See Also

How To Set Up Master Data Sync
External Systems
Integration Queue
Web Services Integrations