Skip to main content

Data Source Troubleshooting

An overview of common issues encountered when using Data Sources, troubleshooting steps, and frequently referenced process solutions.

Written by Viviana
Updated yesterday

When using a Data Source to import Jobs and keep Products updated, you may run into some issues. The following article goes over common issues and their troubleshooting steps. In addition, we will cover frequently encountered Process How-To's.


Check Product Availability

This is a quick tip on how to check if a Product is available on the Data Source and also double-check the Product Properties that are available there.

Head to the top menu, then select Production → Jobs → 'Create Job' → 'From Scan'

If you get the following error message, then the product is not part of the Data Source file(s), and we suggest double-checking the file itself to confirm the Products availability.

If the product is available on the Data Source file, you will get the following view after scanning/manually inputting the code:

On the left side, you will see all of the properties that are available on the Data Source– allowing you to double-check the values.

Property Values Not Updating

You may have noticed that once a Product reaches the 'Done' status, some properties do not continue to update with the Data Source. One potential reason this would occur is that the properties you are trying to update are 'System Properties.'

System Properties

While you can update a custom property even after the product reaches the 'Done' status, properties that are set as 'standard' in the system can no longer be changed after the Product has been delivered to the Asset Delivery location.

View System Properties

  • Product:

    • Brand

    • Category

    • Color

    • Color Reference Url

    • Product Code

    • Product Created Date

    • Product Display Image

    • Product Name

    • Style Code

    • Vendor Material Code

  • Sample:

    • Sample Code

    • Sample Display Image

    • Sample Name

    • Sample Return Date

    • Size

Protected System Properties

In addition to these properties that can not be updated after Asset Delivery, some are further protected and can not be updated via Data Source at any point after initial import.

View Protected Properties

  • Product:

    • ProductCode

    • Category

    • Color Reference URL

    • Product Created Date

  • Sample:

    • Sample Code

UTF Encoded Values

It's also important to remember that Creative Force only supports the encoding type 'UTF-8.' If your data/values are of an alternate type, such as Latin encoding, the data will not be imported or displayed in Creative Force.

Remap Existing Data Source Columns

To check the mapping columns, go to Studio Settings → Data Source. Hover over the Data Source you want to check and click Actions → Mapping Column.

When you have unmapped columns on a running Data Source, you can remap those and click ‘Save’. You will then see further sync options; the logic for these will be explained in the ‘Mapping Sync Options’ section of this article.

Adding New Columns

The data you would like to ingest into the system may change from time to time. Depending on the type of data and change required, you may sometimes need to add additional columns to the Data Source file.

There are different ways to achieve this and different steps you should follow based on the file type you use. We’ll guide you through the different methods below.

⚠️ Important: For any methods below that require updating settings or uploading a new file, you will need to re-map the existing columns for CF to validate the file.

Add Column (JSON File)

When using a JSON file to import and keep Products updated, if you would like to add a new property to be mapped:

  • Ensure that on the updated Data Source file, the very first product entry in the file contains a value for the new property you are adding.

  • The changes will then reflect on any new Product that is being imported into the system.

If you want to have the newly added property available on Products that already exist in the system, you will want to follow the Manual Update Process via the Product-level or Job-level 'Update from Data Source' action.

Add Column (No Delta Files)

If you want to add a new property to your existing Data Source file that does not use Delta File updates, you have two immediate options.

  1. Upload a new Data Source file

    • 'Edit' the Data Source in the Studio Settings

    • Change the current file to a new file that already has the desired changes

    • 'Save' the changes

    • 'Actions' → 'Mapping Column' → Remap all properties → 'Save'

  2. If you want to keep the existing file:

    • 'Edit' the Data Source in the Studio Settings

    • Make a change to the current Data Source settings (eg, the File Path).

    • 'Save' the changes

    • Re-enter the settings and change the setting back to how it was previously

    • 'Save' once more

Add Column (With Delta Files)

When using the 'Update With Delta File' method for your Data Source, and wanting to add new properties.

  • Add the new property column to the latest Delta File

  • Add the new property column to the original (main) Data Source file

Add Column (Gateway API)

When you go to the Data Source Mapping menu, you will see the 'Add New’ button.

Enter the column name and select a corresponding property in Creative Force to map, then ‘Save’. You will then see further sync options, which will be explained in the ‘Mapping Sync Options’ section below.

Mapping Sync Options

After saving the updated column mapping using the steps above, you will be prompted to select one of the following options:

Apply New Mapping to Future Updates

By selecting this option, the updated column mapping will be automatically applied to all Data Source syncs or updates moving forward. Existing product records from previous syncs will remain unchanged.

⚠️ Important: When this option is selected, existing product records will not be retroactively updated to reflect the changed mapping.

This works best if you are planning to capture a new data point moving forward and do not want to affect the existing product data.

Sync Existing Data Source Files

By selecting this option, the updated column mapping will be synced to all existing Data Source records, including delta files, if applicable.

📝 Note: Completion time will vary based on size. Please note that when you have a large Data Source or a large number of Delta Files, the sync may take longer to complete.

Once the sync is completed and the Data Source status returns to 'Data Ready,' then Products and Samples can be manually updated with the new mapping applied by following the 'Manual Update Process' detailed in the next section.

Manual Update Process

There are two options to perform a manual update, and each is described below.

Product-Level Manual Sync

Head to the Product View → Find the Product you would like to update with information in your Data Source → Then, select the 3-dot menu → and 'Update from Data Source.'

Job-Level Manual Sync

Head to the Job View → Find a Job under a Workspace assigned to your Data Source → Then, select the 'Actions' button → and 'Update from Data Source.'

Error Messages

There are a few common error messages that can come up when working with Data Sources. These errors will be related to an unexpected status being returned in the Data Source section of your Studio Settings.

Product Code Not Found

Despite having the Delta files named correctly, you can sometimes encounter this error. Typically, this is found to be caused by the columns of the Delta files and the Main file no longer matching as expected.

🗣️ Tip: Be sure to always use the same naming convention for column headers throughout each file. This includes case sensitivity and spacing.

After correcting any variances between the two files, the issue should resolve during the next sync attempt.

No New Delta File

When seeing this error message, it can be an indication that the file name of the Delta File has not been set up correctly. Please make sure to follow the naming convention tips as shown below:

  • The filename must always have an increment for Creative Force to know which file is the latest. We suggest naming the files with a date/time stamp in the format YYYYMMDD. Example: Delta_20230602.​

  • The headers of each column in the Delta files must exactly match those of the original (main) file.

  • New property columns need to be added to the latest Delta file, plus the original (main) file.

Cannot Sync

A 'Cannot Sync' message will be shown under the status when specific requirements are not being met by the system. Hover over the status to see the related error in full.

The error may refer to one of the following limitations or requirements:

  • Each Delta File should not be larger than 50 MB.

  • There is a maximum limitation of 10,000 Delta Files.

File Not Found

A scheduled sync was completed, but the expected file was not found in the path as expected.

To resolve this, please verify that the file is currently in the exact location the path is set to in the Data Source configuration settings.

Did this answer your question?