Struct Docs
Struct.PIM 4
Struct.PIM 4
  • Struct PIM Documentation
  • API Reference
  • Latest updates from Struct HQ
  • Latest updates in Documentation
  • Fundamental concepts
    • Get familiar with Struct PIM
    • Catalogues & categories
    • Products & variants
    • Attributes
    • Product structures
    • Identifiers
    • Global lists
    • Localization & segmentation
    • Revisions & changelog
    • Publications
    • Supplier onboarding portal
  • Tutorials
    • Helpful guides
      • How to search efficiently
      • How to use Import
        • How to import products
        • How to import data into a list property on entities
        • How to import categories
        • How to import with media
        • How to use File templates
    • Example projects
      • Working with the API
  • Integration
    • Integrate with Struct PIM
    • Web API
    • Webhooks
  • Media format
  • API Reference
    • Introduction
    • Endpoints
      • AssetFolders
      • Assets
      • AssetTypes
      • AttributeGroups
      • Attributes
      • AttributeScopes
      • Browse
      • BusinessUnits
      • Catalogues
      • Categories
      • Dimensions
      • Exports
      • EnrichmentInsightSetups
      • GlobalLists
      • Languages
      • Maintenance
      • Miscellaneous
      • Messaging
      • Permissions
      • Products
      • ProductStructures
      • Publications
      • Transactions
      • UserGroup
      • UserRoles
      • Users
      • VariantGroups
      • UserTasks
      • Variants
      • Webhooks
      • Workflows
      • Models
Powered by GitBook
On this page
  • Before importing
  • Starting the import
  • Mapping your data
  • The file contains new categories
  • Approve changes
  • Resulting category tree
  1. Tutorials
  2. Helpful guides
  3. How to use Import

How to import categories

Learn how to import categories from beginning to end

PreviousHow to import data into a list property on entitiesNextHow to import with media

Last updated 1 day ago

Before importing

A prerequisite to importing is having an excel spreadsheet with the data organized in named columns. For this tutorial we have a made a simple spreadsheet containing information about a clothing tree.

In this example we have created an identifier called 'ClothingCategoryId' with pattern '{0}' using the property 'CategoryAlias'. In short this means the identifier will have the same value as 'CategoryAlias'.

Read more about creating identifiers on catalogues here: Identifier details

Starting the import

To start importing you choose the excel spreadsheet with the data you want to import, in this tutorial the spreadsheet is called "CategoryImportFile.xlsx".

While it is possible to include media assets when importing, this will not be covered in this guide. For this reason we leave 'Upload assets' untoggled.

Having chosen the correct file and import type you can click the "Start upload"-button to start the import.

Mapping your data

As we are importing categories we choose 'Categories' in the Entity type dropdown.

The file contains new categories

Click the "Next"-button in the right-bottom corner to continue.

Approve changes

Having reviewed the changes you can choose to approve the changes you are satisfied with. Only approved records will be commited.

When you have approved the records you want to keep, click the "Commit import"-button in the bottom-right corner to finalize the import.

You can not approve a child category without approving its parent. Doing this will cause the import to fail as it cannot correctly identify where to put the child.

Resulting category tree

In addition, if you want to import a tree structure, you need to give the system a way of identifying parent when importing. One way of doing this is adding an to the you are importing the tree under.

Next you need to choose the correct Import type. When importing , , variant groups or the 'General Excel Import' type is used.

Having clicked the "Start upload"-button you are presented with a new page. This is where you will map your excel columns to data fields on .

Next is mapping the actual data. In this tutorial we map our 'Reference' column to 'Category Alias' as this is the we are using as that will identify which are parents of which child . This is also used as key as it uniquely identifies the .

The 'Name' column is mapped to 'Category Name (da-DK)', this is the we use as Display name for the .

We leave 'Product reference' empty, as this will be used to map child to their parents and is not an that exists on the .

If no with the key exists, new will be created for each unique key you are trying to import. If the excel spreadsheet contains new you will be prompted to map their parent-child relations and choose the to create them under.

We are keeping the reference to the parent in the column 'Parent reference' and want to map it to the unique 'ClothingCategoryId' that exists on the 'Product'.

At this point you are shown a 'Review changes'-page. This page will show you the amount of new and updated . New will be denoted by having a blue 'New'-tag in the key column whereas existing will show their current value.

that will be changed are colored green to easily distinguish between that will remain the same and that will change.

In this tutorial we are importing all new , so everything is shown as green.

The import from this tutorial will result in the following tree under the 'Product'.

categories
identifier
catalogue
category
categories
products, variants
global lists
categories
attribute
identifier
categories
categories
category
attribute
category
attribute
categories
attribute
categories
categories
categories
categories
catalogue
identifier
catalogue
categories
categories
categories
Attributes
attributes
attribute
categories
category
catalogue
categories
category
Excel spreadsheet with headers and data
Identifier on catalogue
Import page
Data mapping
The file contains new categories
Approve changes
Category tree