---
title: "Schedule Tags"
description: "Schedule Tags"
keywords: "Schedule Tags"
url: "https://myrapidi.com/wiki/schedule_tags"
locale: "en"
published: "2018-02-27T11:33:13Z"
modified: "2026-04-07T16:08:51Z"
---

Tags make it possible to run the same set of Transfers for multiple companies without any duplication. The key is understanding how three things connect: **Tag Values** , **Schedules** , and the resulting **named Schedule** that gets created.

## Step 1 : Define your Tag Values

The Tag Values table is where you define what each Tag resolves to for each company. Each row represents one company, and each column is a Tag — such as the connection, currency, or link storage reference.

In the example below, two companies are configured:

| CONN | COMP | CURR | LSCUST |
| --- | --- | --- | --- |
| NAVODATA001 | Cronus DK | DKK | CUST\_DK |
| NAVODATA002 | Cronus ES | EUR | CUST\_ES |

When a Transfer runs for Cronus DK, every Tag in that Transfer - %%CONN%, %%COMP%, %%CURR%, %%LSCUST%, etc. - is automatically replaced with the values from that row.

## Step 2 : Create a Schedule and select a company

When setting up a Schedule, the **Select Tags** dropdown lists one entry per row in your Tag Values table. Simply select the company you want this Schedule to run for ( for example _COMPANY - NAVODATA001: Cronus DK_.) This tells the Schedule which set of Tag Values to use every time it fires.

## Step 3 : The Schedule is created and named automatically

Once saved, the Schedule is automatically given a name that reflects exactly what it does : for example _G\_CUST\_NAVODATA001\_CRONUS\_DK_. The name is derived from the Tag Values, so it is always clear which Transfer group is running, against which connection, and for which company.