iProdSync: Configuring Data Models

Advanced Functions: Associating Tables and Fields

This section requires more technical knowledge, including an understanding of database structures, tables, fields, and data types. Its purpose is to map fields in your database to fields in iProd.

For example, in iProd, the field for the client's business name is called name. If your database table has this field named RagSoc, this is where you configure the system to map data from the RagSoc field in your table to the name field in iProd.

The management of this configuration is controlled through two sections:

CONFIGURE

For each of the three archives, you will need to specify which table from your database will be synchronized with iProd. This includes detailing which fields in the table will be linked, along with other relevant information. Here’s a breakdown:

  1. Archive Selector: Choose between Clients, Items, or Stock.

  2. Database Table: Click to select the table from the list of available tables.

  3. Key Field or ID Name: Click the button to either manually enter the key field or select it from the Associations tab, which will be discussed later.

  4. Last Update Date Field: Similar to the ID field, you can either enter this manually or select it in the same manner.

  5. CSV File Selector: Choose the appropriate data source file in CSV format.

  6. Field Association Status Legend: Provides information on the status of field associations.

  7. Field Association Completion Notification Area: Displays notifications about the completion status of field associations.

  8. Association Structure between iProd and SQL: Shows the current mapping structure between iProd and your SQL database.

  9. Fields Highlighted in Yellow: Indicates fields that are missing associations.

  10. Fields Highlighted in Gray: Indicates fields that, by initial configuration or choice, will not be synchronized.

When you first open the tab, the notification area (7) will show the number of fields still to be associated. Synchronization can only proceed if this message is green, indicating that there are 0 associations left to set.

Note that while it’s not mandatory to associate all fields, the minimum requirement is one field. You can easily mark other fields as unnecessary if they are not required for synchronization.

On this tab, it is mandatory to select the table for all active archives.

If you are unsure about or have doubts regarding the names of the ID and Date fields, they can be omitted at this stage.

 

 

  1. iProd Field List: Displays the fields available in iProd, with detailed descriptions provided in the grid below.

  2. SQL Table Field List: Shows the fields found in the selected SQL table.

  3. Merged Fields List: On the right, you see the iProd field names, and on the left, the corresponding SQL field names.

  4. Merge Button: Both fields from the lists must be selected. Clicking this button removes the names from their respective lists and adds them as a single entry in the Merged Fields list.

  5. Remove or Ignore Association: Select an item from the iProd list and press this button to indicate that you do not want to associate it with any SQL field and do not wish to transfer data. This action will gray out the field in the SQL Name column.

  6. Manually Associate SQL Field: If you know the name of the SQL field but cannot find it in the SQL list, you can enter it manually here.

  7. Set as ID Field: Use this option to designate the selected SQL field as the ID field.

  8. Set as Last Update Date Field: Use this option to designate the selected SQL field as the Last Update Date field.

  9. Undo Field Merge: Reverts the merged fields to their respective lists, allowing you to choose other associations.

  10. Merge Progress: Displays the fields that have been merged, with their previous colors updated to reflect their status.

A summary message above the iProd field list indicates how many associations are still required to complete the configuration.

Save Configuration

Once all definitions are complete, save the configuration and run some sync simulations to ensure that the setup is accurate and stable.