Page History

...

Include an input step to define where to extract your data from. The following types can be used:

Section

Column Image RemovedImage Added Column . Icon Input source Description Step Description Image Added Third-party Connector To extract data from a single third-party connection table. The connectors currently supported are: Google Analytics, Google Sheets, and Salesforce. Image Added Freehand SQL Use this method to import data from a database using an SQL query. Image Added Single table This input step can be used to import data from a single database table. Image Modified Delimited file This input method is used when extracting data from a delimited file (that is, a file with separators). Image Removed Freehand SQL Use this method to import data from a database using an SQL query. Image Modified Report Use this method to use a Yellowfin report as the source of data. This method accepts 2-dimensional reports, but not multi-dimensional ones. The following types of reports are currently not supported: Jasper, SSRS, and BIRT Image Removed Single table This input step can be used to import data from a single database table. Image Removed Third party connector To extract data from a third-party connector. The connectors currently supported are: Google Analytics, Google Sheets, and Salesforce.

Click here to learn more about these steps and how to configure them.

...

Use a transformation step to transform or convert the connected data. Yellowfin includes the following built-in transformations, however more can be added.

Section

Column Image RemovedImage Added Column Icon Transformation type Description Aggregate Step This step transforms your data into a summary form, by applying functions like count, count distinct, sum, average, etc.   Calculated Field This step creates a calculated field based on other fields in the step.   Filter This step is for filtering data in a step.   Merge This step merges two sets of data based on the configured Join Fields.   Split This step duplicates an input dataset to create identical output datasets. Image Added Union This step combines data from two datasets together into a singular field

This section teaches you how to configure each of these steps, along with other types of transformations.

...

Once a step is added to the canvas, right-click on it to see the functions that can be performed on it.

Image RemovedImage Added

These are explained below:

...

1. Right-click on a connection to bring up the menu.

2. Click Edit Flow.
   
   
   
   

3. A popup will appear displaying the data mapped between the two steps. The incoming/source fields (from the previous step) will appear on the left side, and the target fields (for the next step) will appear on the right side.

4. You can perform the following types of actions on the mapping:

5. Auto-mapping: Allow Yellowfin to do the field mapping for you by clicking on the Auto-Map Fields button. The system automatically matches fields based on their names and data type. Note: This feature is ideal for situations in which a connection is deleted and then created again. The fields will not be mapped as before, and using this button will auto-map them correctly.

6. Change mapping: Hover your cursor over a field on the left side, and when the reorder icon appears, click and drag it to match any field on the right side.
   Note: The target field will lose its previously mapped field, which will appear in the unmapped section. 
   Image Removed
    Image Added
   
   

7. Deleting fields: You can delete a field, in which case it will not be sent to the target step and any subsequent steps.

1. Hover over a field on the right side, and when the delete icon appears, click on it.
   
   
   
   

2. On doing so, the matched source field will be added to the unmapped section at the bottom.

3. Delete this field from the unmapped section as well. It will not appear in the target step.

8. Field unmapping: If a field on the left side is deleted first, then the target field will lose its mapping. Similarly, fields can get unmapped when a mapping is changed or reordered. Unmapped fields will have the following warning appear next to them.
   
   
   
   

   1. All target fields are required to be mapped, therefore you can either delete that target field, or drag another field to match with it. The removed field will be added to the umapped section.

9. All unmapped fields appear at the bottom of the popup on the left side (as shown in the example below). Fields in the unmapped section will be sent to the target step, however any data conversions or field transformations previously made on them will be lost, and not be applied to these fields in the target and any subsequent steps. However, previous steps will not be affected.
   
   
   
   

10. Click on the Done button. A confirmation popup will appear, displaying mapping changes made to the flow. 
    
    
    
    

11. Click Confirm to apply these changes.

...