--- url: >- /statelake/tutorials/tutorial-exercises/tutorial-2-import-debtors-into-a-custom-database.md --- # Tutorial 2: Import Debtors Into A Custom Database This tutorial illustrates the simplest example of mapping into a database table. As we did in Tutorial 1, we will again use the Exo database **Data_Demo** as the data source via the **DB Connection** called **MYOB Exo**. And for this tutorial the destination will be a custom database table within the **Statelake** demo database. Because there is no requirement for a **File Definition** or **File Connection**, these will not be defined in this tutorial. In real-life terms, this tutorial examines how to integrate two systems – or how to export records out of an operational database, into a data warehouse or other reporting application. Each step should be fully completed before processing to the next. As well as becoming more familiar with the **Statelake** components and modules, by completion of this tutorial you will be familiar with the process to: * Re-use existing components of a **Statelake Configuration** * Create a **DB Definition** for importing records into a single database table It is most important before you proceed, to check and ensure that all of the training files have been copied as instructed. These files are an essential part of this tutorial. ## Where The Data Is - Database Connections In this tutorial, an Exo database will be used as the source. So, we can re-use the **DB Connection** named **MYOB Exo** that was established for the first tutorial - **Exporting Creditor Accounts Into A Flat File Supplier List**. However, a new connection will need to be created for the destination database table. The first step is to make sure that **Statelake** module **Designer** for your selected configuration **Statelake_Training** is open. In **Manager**, select **Home**, then **Run Statelake Designer**, then select **Statelake_Training** from the drop-down menu and click **OK**. ![](/statelake/images/image-20230419-025818-7ee0ffdc.png) **Designer** will open with an expanded structure tree is displayed on the left side of the screen. ### Create DB Connection 1. Follow the path **Configuration > Components > Data Connections > DB Connections**. Click on **DB Connections** and **MYOB Exo** should be displayed. This connection to the database **Data_Demo** will be used for the source. 2. Clck on **DB Connections** - after completion of Tutorial 1, \_Self and **MYOB Exo** should appear as available connections. Right-click on **DB Connections** and choose **New** from the drop-down list to create a new connection for the destination database **Statelake_Demo**. 3. **New DB Connection** should appear in the connection list. In the **New DB Connection** window the following information is to be entered. 1. **Connection Name** – some source databases will have obscure or convoluted names. This field is the user-friendly identifier name that will appear in the **Statelake** configuration, that references the source database. Enter **My SL DB Demo**. The two tick boxes **Use Config Database** and **Use Config Database Server Only** should be left blank. 2. The screen is then split into two tabs - **General** and **Advanced**. The **Advanced** tab allows you to set other options, but for training purposes, we will be dealing with just the **General** tab. 3. **Connection Type** – select the database engine that is to be used. In this instance, click the radio button **Microsoft SQL Server**. 4. **Server Name** – the server location for the destination database. As you used on the initial login screen to **Microsoft SQL Server Management Studio**, enter the server name which will either be \\STATELAKE, or \\SQLEXPRESS. 5. **Database Name** – the name of the database. Enter **Statelake_Demo**. 6. User **Name** and **Password** – fill these out with SQL authentication details or leave them blank to use Windows Authentication. ![](/statelake/images/image-20230419-025242-80822967.png) 4. Click on the **Test** button in the top left of the window when all details are populated. If the details are all correct, you will be presented with a message “**Connection Test Successful**”. Otherwise, you will see the error reported by the database server. Click **Ok** to proceed. ::: info It is impossible to cover all possible errors that nay come from a database connection because any error would be specific to the type of the database, and each database type may have hundreds of errors that can be generated. If you do not know what they error is, then try searching the web for documentation about errors for the type of database you are attempting to connect to. ::: 5. If the connection test is successful, click **Save** and close the connection module. The **DB Connection** named **My SL DB Demo** will now appear below **MYOB Exo** in the structure tree under **Configuration > Components > Data Connections > DB Connections**. ## What The Data Is - Creating DB Definitions The **DB Definition** tells **Statelake** what the data is, so that the proper fields can be accessed and the data extracted or written correctly. For this tutorial, this means defining the exact information to be extracted, and also identifying how any output file is to be constructed. Sitting under the **Data Definitions** umbrella, **Statelake** uses the **DB Definitions** module to define these data structure components, and to design the database queries for both reading the data out of, and writing in to, any databases. This tutorial illustrates creating definitions for reading the data from the Exo database called **Data_Demo** via the **DB Connection** called **MYOB Exo**, and another definition called **Exo:Debtors Out** for writing into the **Statelake** destination database **Statelake_Demo**. **Designer** will already be open. If not, open the **Statelake** module **Designer** for the selected configuration **Statelake_Training**. An expanded structure tree is displayed on the left side of the screen. The first step is to create a **DB Definition** to read from a single database table as the source. ### Create DB Definition (source) 1. Follow the path **Configuration > Components > Data Definitions > DB Definitions**. Right‑click on **DB Definitions** and choose **New** from the drop-down list. 2. **New DB Definition** will appear in the structure tree. In the **New DB Definition** window the following information is to be entered. 1. **DB Definition Name** – the name that is meaningful and best describes the query/extraction. We will call this **Exo: Debtors Out**. 2. **DB Connections** – this is the name of the source database, identified by the meaningful name that was given in the **DB Connections** module. Right-click anywhere in the blank space in the box to see the **Add** pop-up, and a list of all the found connections will be displayed. Select the one you want from the list – in this tutorial, it will be **MYOB Exo**. You will notice that **My SL DB Demo** and \_Self also appear on the list but these will not be selected at this stage. 3. **Transaction Identification** – leave with the defaults as set. 4. **Duplicate Record Handling** – leave with the defaults as set. 5. **Disable Automatic String Trim** – leave with the default as set. This is ticked. 6. **Save Null Fields as Blank Strings** – leave with the default as set. 7. **Disable SQL Transactions** – leave with the default as set. 8. **Save Blank String Fields as Nulls** – leave with the default as set. 9. **Include Null Values in SQL statement** – leave with the default as set. ![](/statelake/images/image-20230419-030348-e91993e6.png) 3. Click **Design** in the top left of the window. ### Create DB Dataview Query (source) 1. The blank definition designer canvas for **New DB Definition** will display. To start creating your query, click on the **File** menu in the top left corner, and choose **New** (or use the Ctrl+N). 2. The **New Items** window will open and only one item called **DB Dataview** will be displayed. ![](/statelake/images/image-20230419-030454-07c41b3c.png) Click **OK** to add **DB Dataview**. 3. The **Query Designer** window will open. ![](/statelake/images/image-20230419-030640-8982f928.png) 4. The first tab in the **Query Designer** is **Tables**. The upper pane contains a list of available tables in alphabetic order, and the lower pane will display the tables that you select. Scroll down the available tables to **DR_ACCS** (Debtor Accounts) and double-click to select it. It will appear in the lower pane as a selected table, while still remaining in the upper pane list. ::: info You may have to expand the window height to see a greater number of entries. ::: 5. Move to the **Fields** tab, and add the following fields to query by double-clicking on them. The files will not automatically sort or appear in alphabetic sequence. Click on the field list header **Field Alias** to sort in descending order A-Z; click again to change to ascending order Z-A; then click again for a random sort. 1. **ACCNO** (account number) 2. **NAME** (account name) 3. **ADDRESS1** 4. **ADDRESS2** 5. **ADDRESS3** 6. **PHONE** 7. **FAX** 8. **ISACTIVE** ::: info The fields are colour-coded in the **Query Designer**. **RED** indicates that the field is either calculated or is an automatically generated identity such as ACCNO. **PINK** indicates that the field does not allow null values such as with HEAD_ACCNO. ::: 6. As you select fields from the **Available Fields** pane, they will appear in the **Selected Fields** pane, and disappear from the **Available Fields** pane. ![](/statelake/images/image-20230419-031425-421f704d.png) 7. Click on the **SQL** tab to see the SQL query that has been generated. ![](/statelake/images/image-20230419-031528-51c9dc6e.png) It lists the fields you selected and the table they are to be retrieved from. Note that the table name prefixes the field name and is separated by a full stop. ::: info If you make a mistake and click on one of the fields in the **Available Fields** pane more than once in error, or click on a field that you do not want, simply double-click on the field you do not want in the **Selected Fields** pane to de-select it, and it will re-appear in the **Available Fields** pane. ::: 8. Click **OK** at the bottom-right of the **Query Designer** to save the dataview and return to the definition canvas. The configured dataview will display, listing all of the selected fields. The **DR_ACCS** dataview window can be expanded as required. ![](/statelake/images/image-20230419-031740-ad98e7fb.png) ### Preview Your Results 1. You can preview the data that will be returned by the query by clicking on the **Preview** button on the upper left corner (circled). Click **OK** to close the preview pop-up window. 2. Close the definition canvas by selecting **Close** from the **File** menu. You will return to the **Exo: Debtors Out** window. Click **Save** to save and close the module. The **DB Definition** named **Exo: Debtors Out** will now appear in the structure tree under **Configuration > Components > Data Definitions > DB Definitions**. The next step is to create a **DB Definition** to write into a single database table as the destination. Designing this definition is almost identical to the definition you have just created to read from the source table. ### Create DB Definition (destination) 1. Right‑click on **DB Definitions** again and choose **New** from the drop-down list. 2. Again, **New DB Definition** will appear in the tree structure under **DB Definitions**. In the **New DB Definition** window the following information is to be entered. 1. **DB Definition Name** – the meaningful name for this table will be **My SL: Customers In**. 2. **DB Connections** – this is the name of the destination database, identified by the meaningful name that was given in the **DB Connections** module. Right-click in the blank space in the box to see the **Add** pop-up, and a list of all the found connections will be displayed. This time select **My SL DB Demo** from the list. 3. **Transaction Identification** – leave with the defaults as set. 4. **Duplicate Record Handling** – leave with the defaults as set. 5. **Disable Automatic String Trim** – leave with the default as set. This box is ticked. 6. **Save Null Fields as Blank Strings** – leave with the default as set. 7. **Disable SQL Transactions** – leave with the default as set. 8. **Save Blank String Fields as Nulls** – leave with the default as set. 9. **Include Null Values in SQL statement** – leave with the default as set. ![](/statelake/images/image-20230419-032350-ec804ef2.png) 3. Click **Design** in the top left of the window. ### Create DB Dataview Query (destination) 1. A blank definition **New DB Definition** designer canvas will display. To start creating your query, click on the **File** menu in the top left corner, and choose **New** (or use the Ctrl+N). 2. The **New Items** window will open and only one item called **DB Dataview** will be displayed. Click **OK** to add **DB Dataview**. 3. The **Query Designer** window will open. ![](/statelake/images/image-20230419-032525-97678aac.png) 4. The first tab in the **Query Designer** is **Tables**. The upper pane contains a list of available tables in alphabetic order, and the lower pane will display tables selected from this list. You will see as a comparison, there are only a few tables listed in this dataset - **Contacts**, **Customers**, **OrderHeader**, and **OrderLine**. Select the **Customers** table by double-clicking to select it. It will appear in the lower pane as a selected table, but will remain visible in the upper pane. ![](/statelake/images/image-20230419-032729-de765c42.png) 5. Move to the **Fields** tab, and just as you did in the source query, add the following fields to query by double‑clicking on them: 1. **hostId** 2. **customerType** 3. **companyId** 4. **companyName** 5. **phone** 6. **fax** 7. **isActive** 6. As you select fields from the **Available Fields** pane, they will move - appearing in the **Selected Fields** pane, and disappearing from the **Available Fields** pane. ![](/statelake/images/image-20230419-033259-90095e8e.png) ### Setting Field Parameters And Criteria The selected field **hostId** is to be set to be the primary key. 1. On the lower section of the pane under **Selected Fields**, click **hostId** under the **Field Alias** heading to select and highlight the line. The **Field Type** for **hostId** should say **Standard** – in fact, all of the fields in this lower pane default to this value. 2) While the line is selected, select **Primary Key** from the pull-down list beside **Standard** under the **Field Type** heading. ::: info Setting the field **hostId** as the **Primary Key** for this destination dataset enables this field to determine whether incoming data from the source needs to be updated or inserted into the destination database. With this setting, if a record for the incoming **hostId** already exists in the table, then the rest of the fields in that record will be updated as appropriate, based on the incoming data. And if a record for the incoming **hostId** does not already exist, then a new record will be created. If a **Primary Key** is not used, then the **DB Definition** will always create new records i.e. be in insert mode only. ::: 3. Specify the **Display Format** field for **isActive** to be **1**;**0** if it is not already displaying this value. ::: info To ensure that boolean **True** and **False** values are handled correctly, this field needs to be forced to hold data that will be easily recognised and interpreted. So the value is converted into either a bit data type as **1** for **True**, and a **0** for **False**. ::: 4. Click on the **Search** tab. A list of the table fields will display in the upper pane labelled as **Available Fields**. Double-click on **id** to add it to the **Field** column in the lower **Criteria** pane. It will display as **Customers.id** (table.field) and an equal sign = will automatically appear in the **Operator** column. Set the **Value** to -1 (minus one) on this line, to ensure that the **DB Definition** is empty when it is loaded into the **Map**. If this destination dataset holds any data, then **Statelake** will produce an error, so to successfully insert or update data into a populated table, the search criteria is set to a value that will not exist in the table (such as -1). 5) Click **OK** at the bottom-right of the **Query Designer** to save the dataview and return to the definition canvas. The configured dataview **Customers** will display, listing all of the selected fields which can be expanded as required. 6) Close the definition canvas by selecting **Close** from the **File** menu. You will return to the **DB Definition** window. Click **Save** to save and close the module. The **DB Definition** named **My SL: Customers** In will now appear in the structure tree under Configuration > Components > Data Definitions > DB Definitions. ## What To Do With The Data - Creating Maps There have now been two **DB definitions** created for this tutorial., so the next step is to create a **Map** to pull the data from one, into the other. **Designer** will already be open. If not, open the **Statelake** module **Designer** for the selected configuration. An expanded structure tree is displayed on the left side of the screen. ### Create The Map 1. Follow the path **Configuration > Components > Maps**. Right‑click on **Maps** and choose **New** from the drop‑down list. 2. **New Map** will appear in the tree structure. The **New Map** window contains two tabs - **General** and **Parameters**. The **Parameters** tab allows you to set other options, but for training purposes, we will be dealing with just the **General** tab. The following information is to be entered for the main map. 1. **Map Name** - this is the meaningful name that will identify the extraction process. Enter **Export Customers To SL DB**. 2. **Source Data** – highlight the **DB Definition** radio button. 3. **Definition** – the **DB Definition** that was created for this configuration called **Exo: Debtors Out** can be selected from the pull-down list. 4. **Destination Data** – highlight the **DB Definition** radio button. 5. **Definition** – the name of the **DB Definition** that was created for this configuration called **My SL: Customers** **In** can be selected from the pull-down list. ![](/statelake/images/image-20230419-034853-fe7e4967.png) ### Open The Map 1. Click the **Design** button in the top left of the window to open the map designer window **New Map**. 2. The **New Map** screen is split into five distinct panes beneath the search bar. 1. **Source** is split into two panes with **Source Data** and **Parameters** tabs. This is the definition of the source that data is to be read from. 2. **Destination Data** is also split into two panes. This is the definition that the data is to be written to. 3. **Field Events** on the right side of the screen. The events of the selected dataset or record. 4. **Scripting Area** beneath the **Source Data** and **Destination Data** panes. Where the script of each event is displayed and edited. 5. **Compiler Messages** below the **Scripting Area**. Messages that are returned by the compiler. In this tutorial we will link the source dataset table **DR_ACCS** to the destination **Customers** dataset. **DR_ACCS** is already showing in the **Source** pane, and **Customers** is already showing in the **Destination Data** pane. ![](/statelake/images/image-20230419-035129-f9b5ebba.png) ### Link The Datasets And Populate The Map 1. Link the two datasets by dragging the **DR_ACCS** source dataset and dropping it onto the **Customers** destination dataset. Once a successful link has been established you will see the established link appear in the **Scripting Area**, where the **LinkedDataEvent** code has been automatically generated. Close up of the code as below. ```pascal procedure LinkedDataEvent(var LinkedData:TdaQueryDataView); // Customers begin LinkedData := DR_ACCS; end; ``` 2. A list of events has also appeared in the **Field Events** pane, and this has been renamed to **Events For Customers**. The file icon beside the **LinkedData** event is now coloured **GREEN** which indicates a successful compilation for this event. If the icon was **RED**, this would indicate that the code was not successfully compiled. ### Link The Fields 1. Click on the **DR_ACCS** table to list the fields in the **Field** pane under **Source Data**, and click on the **Customers** table to display the fields in the **Customers** table under **Destination Data**. Now link the fields using the same drag and drop technique used previously: drag the fields from the **Source DR_ACCS** field and drop it onto the fields for the **Destination Data** table **CUSTOMERS**, making sure that the destination field is highlighted before dropping the source field onto it else the link will not be successfully established: 1. **ACCNO** to **hostId** 2. **NAME** to **companyName** 3. **PHONE** to **phone** 4. **FAX** to **fax** 5. **ISACTIVE** to **isActive** 2. For each successful field drop, the colour of the field name in the **Destination Data** pane changes to **GREEN**, and an **OnMapEvent** procedure appears in the **Scripting Area**. In the **Field Events** pane, a set of events for each field has appeared, and each successful link is indicated by the **OnMap** event file icon being shown in **GREEN**. ![](/statelake/images/image-20230419-043411-d34faf41.png) 3. Click on the **customerType** field in the destination area, and then in the **Scripting Area** to manually specifiy the mapping for the field. The following code will be manually generated: ```pascal procedure OnMapEvent(var Value:variant); // customerType begin Value := end; ``` 4. Append to the third line and type ‘EXO’; (quote EXO quote semi-colon) immediately after the Value :=. Now click on **customerType** in the destination pane, and when you click out of the **Scripting Area**, if you are prompted to save your changes, click **Yes**. ![](/statelake/images/image-20230419-043618-a761b878.png) The **Compiler Messages** area should tell you that the compile was successful. If not, check your spelling and try again. 5. In this tutorial the field **companyId** is going to be exactly the same as the field **hostId** in the destination dataset. Therefore, you are able to map the value of **companyId** from the already mapped **hostId**, rather than mapping **DR_ACCS:ACCNO** again. There are a couple of steps to perform to achieve this. 1. Click on the **companyId** field, and then click into the blank **Scripting Area**. A blank **OnMapEvent** script will be generated. 2. Right-click on the **hostId** field in the destination area. You will see that the cursor shape has changed into a greyed box and that you are in effect actually dragging the field. 3. Left-click in the **Scripting Area** at the end of the 3rd line after Value :=. to append the value **D\_Customers\[‘hostId’].Value** to the line. 4. The script has now become: ```pascal procedure OnMapEvent(var Value:variant); // companyId begin Value := D_Customers['hostId'].Value; end; ``` 5. Type a semi-colon at the end of the line after .Value to complete it. Click on **companyId** in the destination pane and when you click out of the **Scripting Area**, if you are prompted to save your changes, click **Yes**. The **companyId** field will change to **GREEN**. ![](/statelake/images/image-20230419-044222-a0b3ec79.png) 6. In the source, the **ISACTIVE** field is currently of the type **String**, while the **isActive** field in the destination is of the type **Boolean**. To assign the value in one field to another field, the types must be the same - you cannot cross-type. So we cannot just simply assign **DR_ACCS:ISACTIVE** to **Cutomers:IsActive**. The **ISACTIVE** field values in the source dataset will need to be translated into **Boolean** to match the destination field type. 1. **ISACTIVE** with a string type can have either **Y** or **N** values. Click on **isActive** from the destination dataset to load the script into the **Scripting Area**. 2. Type in a decision tree to change the script code to the following, as illustrated below. Note that the **if** line, the **else** line, and the line Value := true do not have a semi-colon on the end because neither line is the end of the IF statement (ELSE is following it). ```pascal procedure OnMapEvent(var Value:variant); // isActive begin If DR_ACCS['ISACTIVE'].AsString = 'Y' then Value := true else Value := false; end; ``` 3. Click **isActive** in the destination area to save the script. Respond **Yes** to the saving the change of script. ![](/statelake/images/image-20230419-044751-66aa7c56.png) 7. **Save** the **Map** and commit all of the mapping and scripting by clicking **Save Map** in the top right corner. Select **OK** to close the successful save message. then click on the **Close** button to close the map designer window. 8. To commit all the mapping and scripting, click on the **Save** button to save and close the mapping module. The **Map** named **Export Customers To SL DB** will now appear in the structure tree under **Configuration > Components > Maps**. ### Test The Map 1. Now test the **Map** to ensure it is working: 1. Open the **Maps** module again by clicking on **Export Customers To SL DB**, and click on the **Design** button. 2. The **Export Customers To SL DB** map designer screen will display, with only the **Source** data **DR_ACCS** showing, and **Customers** showing under **Destination Data**. 3. Click **Test Map** in the top right corner of the screen, to execute the map in memory and generate a processing log which is then presented in a preview pane. A successful test will display the log with a light green background, but if an error is encountered, then the log background will be pink. ![](/statelake/images/image-20230419-045144-f69eb1e5.png) 4. Close the pop-up preview of the log and the destination definition query **Export Customers To SL DB** will be displayed on the canvas. Click on the **Preview** button to view the list of all of the processed records. ![](/statelake/images/image-20230419-045218-0089fc0b.png) 5. Using the **X** in the upper right corner, close the **Preview Data** pane, or click **OK**. 6. Select **File Close** on the canvas, then the **Close** button on the map designer screen, followed by the **Cancel** button on the **Export Customers To SL DB** data entry window. The **Map** has now been configured to insert records into another dataset, and the links have been tested in memory to ensure that the map has all the information required for a successful extraction. However, no actual database activity has been generated. The next step pulls all the configured components together to produce the destination dataset ## What Action To Take - Creating An Action The final step is to pull all the definitions and configured components together to form an executable process to follow the **Map** and produce the destination database. This process is called an **Action**. While the details for an **Action** can be created manually, **Statelake** can also generate the **Action** for you. **Designer** will already be open. If not, open the **Statelake** module **Designer** for the selected configuration. An expanded structure tree is displayed on the left side of the screen. ### Create The Action Automatically 1. Follow the path **Configuration > Components > Maps**. Click on **Maps** to expand the tree. Right‑click on the map you have just created called **Export Customers To SL DB**, and choose **Create Action** from the drop‑down list. All the relevant fields will be populated and components will be automatically added to this **Action**. ![](/statelake/images/image-20230419-053344-2cdc1573.png) There is no need to do anything with this window, except select **Save** on the top right corner to close the module. The **Action** named **Export Customers To SL DB** will now appear in the structure tree under **Configuration > Actions**. ### Run The Action 1. To run this **Action**, click on **Actions**, then right-click on the **Export Customers To SL DB Action**, then select **Run Action** from the available options. 2. A window will pop-up showing the processing steps in a preview log, which will itemise and show the steps that were completed, how many records were extracted and processed, and where the destination file was saved. When the action has been completed a status message will pop-up on screen indicating that processing is complete, and advising whether the process was successful or an error was encountered. A successful **Action** will offer two choices – click **Yes** to review the log, or click **OK** to close the log without review. ![](/statelake/images/image-20230419-055222-f7333b7e.png) 3. To close the log after review, click the **X** in the upper right corner. ::: info **Logs** can be re-opened at any stage as many times as required. To review a **Log** from the **Manage Logs** window, double-click on the **Log** entry as required. To drill into any line on the **Log**, double-click on the line to see more detail. ::: The process is now complete, all modules have been closed, and the structure tree will be the only item on the **Designer** screen. ### Reviewing The Log The **Logs** from the running of all **Actions** can be accessed and reviewed at any time. 1. Click on **Logs** and the **Manage Logs** window will open, and a list of all logs written will appear. ![](/statelake/images/image-20230419-055259-5e4c1895.png) 2. Double-click on the log **Export Customers to SL DB** under the **Action** column to open the log. 1. Click on the **SQL** tab to see the SQL executed against the destination database. You can see how the records were inserted into the destination database. ![](/statelake/images/image-20230419-055350-fb8f50c1.png) 2. Close the log by clicking the **X**. Then close the **Manage Logs** window by clicking the **X** in the top right corner. 3. If you run the **Action** again and then re-check the log – you will see another entry has been written to the list. ## Summary You have now successfully read data from one dataset and written that data into another. In summary these are things that have been achieved for this configuration in this tutorial: 1. Database definitions have been configured to enable writing into a dataset. 2. Several simple mapping scripts have been introduced. 3. The use of a decision tree in the mapping script. 4. Data type conversion during scripting. 5. Querying databases from the map during processing. ## Quick Recap Quiz This was a complex tutorial, so you have done well! Here is an easy recap to test your knowledge. 1. What module would define the tables and columns that you want to read from, or write to, a database? a. Map b. DB Connection c. DB Definition \2. What is a decision tree? a. Available options b. Possible outcomes c. Isaac Newton’s apple tree \3. What is a primary key? a. Main data identifier b. How to unlock a record c. A password \4. In what **Statelake** module would scripting primarily be employed? a. Action b. Map c. File Definition \5. What is the purpose of an **Action**? a. To start processing b. To create a file structure c. To define a database \6. Where would you find a **LinkedDataEvent**? a. File Definition b. Action c. Map \7. In the absence of a primary key, what is the default behaviour of a **DB Definition** when the database is used as a destination? a. Update b. Create c. Delete \8. What module would you use to define a database name and access credentials? a. DB Definition b. Action c. DB Connection ## Next Steps You have done really well and made excellent progress! The next tutorials in this series are: * **Tutorial 3 - Importing XML Purchase Orders Into A Database** * **Tutorial 4 - Extracting XML Invoices Out Of A Database** * **Tutorial 5 - Statelake Magic SQL** * **Tutorial 6 - Import CSV Purchase Orders Into A Database** * **Tutorial 7 - Exporting And Importing Configuration Data** ::: details Quick recap quiz answers 1. c 2. b 3. a 4. b 5. a 6. c 7. b 8. c ::: How well did you fare?