Transfers: General Information

 

Overview

Under "Transfers" you can create/set up the needed transfers of data. One Transfer regards transfer of one table to another.

 

A Transfer contains the following fields:

 

Code:

  • Give the Transfer a unique ID.
  • Use capital letters, underscore and numbers only.
  • The Transfer code determines the order that transfers are run when they are in a group. It's a very good idea to use a naming convention that keep semilar transfers listed together. We generally use names like "CUST01_NAV_2_CRM_ADD" and "CUST02_CRM_2_NAV_UPD" and "ITEM02_NAV_PRICES_2_CRM".

Description:

  • Fill in a descriptive text.
  • The text specified here will be written to the Activity Log and to the screen when running the Transfer from the command line prompt.
  • Make the description as meaningful as possible, so that it is easy to see what the Transfer regards, and if the Transfer includes special features such as Gather, Scatter or a SubTransfer etc.

Status:

  • Choose between the different statuses: 'Implementing', 'Testing', 'Ready', 'Archived'.
    Read more about Transfer Status

Group:

If you want the Transfer to be part of a group, you can by pressing the lookup button to choose the group from a list.
 
Source:

  • Choose which Connection data should be transferred from.
  • You can press the lookup button to choose the Connection from a list.

Source Layout:

  • Choose which Connection on the source side should be used to find or lookup table or field names

Destination:

  • Choose which Connection data should be transferred to.
  • You can press the lookup button to choose the Connection from a list.

Destination Layout:

  • Choose which Connection on the destination side should be used to find or look-up table or field names

Source Table:

  • Specify which table data should be transferred from.
  • When you start typing a table/object name here, Rapidi will return a list of tables/objects that match what you have typed so far.

Destination Table:

  • Specify which table data should be transferred to.
  • When you start typing a table/object name here, Rapidi will return a list of tables/objects that match what you have typed so far.

Link Storage:

  • Specify which Link Storage should be used.
  • Choose from the dropdown which TAG or CONNECTION is available.

 Enabled:

  • You can enable or disable the Transfer.
  • If you mark this field, Rapidi will run the Transfer when instructed to do so (for example if the transfer is part of a group and the group is scheduled to run).
  • If you leave the field unmarked, the Transfer will not run.

Update:

If you mark this field, Rapidi will update existing records in the destination table.


Add:

If you mark this field, Rapidi will add not-yet-existing records in the destination table.


Delete:

If you mark this field, Rapidi will delete the records in the destination table that does not exist in the source table anymore.


Actions:

If you want to make use of the special feature "Actions" you mark this field.

Move:

By marking this field, Rapidi will copy all the records of the source table to the destination table and then automatically delete all records in the source table.


Delete All:

  • If you use Delete All, all the records of the destination table will be deleted first and then data will be transferred as specified within the Transfer.
  • Doing this on Transfers where you know that all records in the destination can be deleted, will greatly improve performance on most systems/databases during transfer when combined with "Disable Dest. Lookup".

Auto Generate Key:

  • If the Connection you want to transfer to/from is of the type Navision 3.56, Navision Financials, Navision Attain, MBS-Navision, or MS Dynamics NAV, and if the data you want to transfer does not have a primary key, you can have Rapidi generate one.
  • When using Auto Generate Key, it is required that the last field in the primary key on the destination table in question is an Integer field.
  • The Auto Generate Key feature will then do a lookup in the Destination Table with filter set on all the fields in the primary key except the last field (so you need to have these fields as Dest. Filters or Table Link), then find the last record and take a number from that as a starting number. It will by default increment by 1 and the default start number is 0 (so that the first record will have number 1). The default start number and increment value can be changed in the Rapidi.CFG file for the RapidiConnector - please contact the Rapidi support team for help with this.
  • Auto Generate Key can be used both on main transfers and on Sub-transfers. A lookup for the last (highest) number will be done each time the filters change - typically for each record when used on a main transfer and once every time a sub-transfers is running.
  • The Auto Generate Key feature can also be used with MS-SQL or MySQL - in this case, a unique id (UUID) is generated.

Disable Dest. Lookup:

  • If you use "Delete All" or you know for sure that the records you are transferring do not exist in the destination table, you can mark "Disable Dest. lookup". This will greatly improve performance since Rapidi does not have to check if the records you are transferring exists in the destination table. On some systems/databases, this will more than double the performance.
  • If you are using Salesforce.com as Destination, the Disable Dest. Lookup in combination with Update and Add will trigger the use of the UPSERT facility in Salesforce.com. This allows us to send all records to Salesforce.com and let Salesforce.com decide if it's an existing record or a new record. This only works if the Table Link consists of just one field and if this field is marked as External ID in Salesforce.com. Please note that in the statistics in Rapidi all records sent like this will show as either Added or Updated - If it's an existing record, it will count as an updated record.
  • Using this facility is greatly recommended whenever possible as it greatly reduces the number of API calls done to Salesforce.com.

All Fields:

By marking this field, all fields with the same name in both Source and Destination will be transferred.

 

Continue on Error:

  • By checking this field Rapidi will continue to transfer data even if some records fail to be saved to the destination system (due to data errors or validation errors in the destination system).
  • The erroneous records are skipped and a log entry concerning each of these records can be found under the 'Data Errors' sub-page under 'Logs'.
  • This feature might be useful if you have a large amount of data you wish to transfer all at once regardless of any validation errors.
  • However, we recommend using this feature with caution (especially in combination with source control) as when enabled the erroneous data is NOT transferred automatically again. You will have to take action and fix the data (change the records) in the Source system in order for Rapidi to try to transfer these records again.

Source Control:

If you want to transfer only the records that have been changed since the last transfer, you can make use of the feature, Source Control.

 

Actions:

If you want Rapidi to perform an update, add or delete on specific records, you can make use of the feature Actions.

 

Triggers:

Triggers in Rapidi are useful when it is necessary to perform some kind of data manipulation on the data that is about to be transferred or after the data has been transferred.

 

  1. Getting Started
  2. Documentation
  3. HowTo
  4. Standard Integrations

 

Service News can now be found on our Product Updates Blog 

 

Remember to Subscribe to our Product Updates Blog to receive updates and product news.

 

 

 

 

Wheeled by Wagn v. 1.9.1