You will create one extract for each Rapidtrade supplier you have configured. In our example, if you have a TEST and LIVE system, then you will setup 2 extracts.
For each extract, you will need to enter you Rapidtrade credentials for the individual suppliers.
If you have not already done so, then run an initialization.
If previously, you used the -remember flag, then you do not need to enter the -org or -orgpassword flags.
rapiddump -org=widgitcompany -orgpassword=mypassword -init
2. Entering Rapidtrade credentials
You are now required to enter the Rapidtrade credentials for the supplier you are extracting data to.
3. Choose type of extract
Choose the type of system you are extracting from.
This can be from our pre-defined set of ERP systems
Or you can choose from either:
- Rest - GET
- Rest - POST
You will be
- Giving your extract a name
- Giving the connection a name
- Enter your connection string (If MYSQL or MSSQL)
The sample SQL or POST json will now be downloaded for you to the "files" folder.
4. Settings for each table
You will now need to answer questions for each table that needs to be extracted. Below, we have pressed enter through each question so the default is taken.
Your initial extract is now complete. See below, in the files folder, your sample SQL or POST/JSON will be downloaded.
Take note of the SQL files that were downloaded into the files and move onto the next section.
5. Testing the local SQL files
You wil now see your sample SQL files that can be used to run a basic extract out of your ERP system in the 'files' folder. You can now edit these in your favourite editor. The SQL files in the 'files' folder allow you to make changes and test these using the -op=test flag.
These changes will not be live and allow you to test changes to your SQL, till you are happy with your changes.
You can test each of your local SQL changes using the following command. The -local is important as it tells rapiddump to test using the local SQL files in the 'files' folder. On completion, the results will be saved in a CSV format in the working folder.
rapiddump -extract=SysproTest -table=Accounts -op=test -local
6. Saving SQL files to Rapiddump
Importantly, rapiddump will not use the SQL files in the local working folder when it runs. As mentioned previously, the SQL files in your files folder allow you to test changes using the above flags. As such your SQL files need to be saved to rapiddump before you can do your first run.
rapiddump -extract=SysproTest -table=Accounts -files=save
7. Testing SQL files in Rapiddump
You can test the SQL files in rapiddump pretty much the same as (5) above, except you will leave off the -local flag. This is an important step as you are making sure that any changes mades to the sql files in the 'files' folder have been saved to rapiddump.
Again, your results will be stored in a CSV file in the working folder.
rapiddump -extract=SysproTest -table=Accounts -op=test
Your setup is complete and you can move onto the next chapter where you will run your extract.