SharpSync
  • Welcome
  • Fundamentals
    • Getting Started
      • Registration
      • Landing Page
      • Support
      • Subscription
    • Data Sources
    • Property Mappings
      • Adding Property Mapping
      • Property Mapping Settings
    • Rules
      • Import / Export
        • Append text
        • Calculate number
        • Export manipulation
        • Format as decimal number
        • Prepend text
        • Remove property
        • Replace all instances
        • Replace first instance
        • Round to nearest X
        • Select from JSON
        • Set cell value
        • Set empty cells
        • Text manipulation
      • Display
        • Number between
        • Text contains
        • Text ends with
        • Text evaluation
        • Text is a number
        • Text is exactly
        • Text is in list
        • Text is not a number
        • Text is not empty
        • Text is not in list
        • Text length between
        • Text length is exactly
        • Text maximum length
        • Text minimum length
        • Text not contains
        • Text not ends with
        • Text not starts with
        • Text starts with
      • Advanced Scripting
    • BOM Comparison
    • Data Safety
    • Troubleshooting
      • Duplicate component paths
      • OAuth 2.0
  • Data Sources
    • Autodesk Inventor
    • CSV
      • Getting Started
      • Importing a Bill of Materials (BOM)
    • MS Dynamics 365 Business Central
      • Getting Started
      • Item Fields Json & Internal Names
      • Resource Fields Json & Internal Names
      • List Names For nestedObject Mappings
    • NetSuite
      • OAuth Setup
        • Permissions
      • RESTlet Script Setup
        • SharpSync RESTlet Script
      • Thumbnail Folder Setup
      • Authentication + Configuration
      • Common setup
        • Configure quantity mapping
        • Configure accounts mappings
        • Configure itemType mapping
        • Configure isPhantom mapping
        • Configure subsidiary mapping
        • Configure price mapping
        • Configure Where Used Link mapping
        • Configure thumbnail mapping
        • Read-Only NetSuite Fields
        • Common Mapping Rules
        • Common List names
      • Advanced Bill of Materials
      • Configure Routings
      • Integration tips
      • Troubleshooting
    • Odoo
      • Getting Started
        • Authentication + Configuration
        • Debugging tips
      • Common Setup
        • Map BOM Codes
        • Map BOM Types
        • Map Attribute Values
          • Reading Attributes - Overview
          • Display All Attribute Names
          • Display Single Attribute Values
          • Writing attributes
      • Product Management
      • Hosting Options
      • List Names
      • Permissions
      • Troubleshooting
    • Onshape
      • Getting Started
      • Setting up Derivatives
    • Propel PLM
      • Getting Started
    • SolidWorks
    • SolidWorks PDM
      • Downloading and installing the add-in
      • Configure the add-in
      • Setting up the Solidworks PDM Web 2
      • Troubleshooting
      • Submitting a BOM for update
  • Advanced
    • Derivatives
  • User management
    • User Management
    • Application Permissions
Powered by GitBook
On this page
  1. Fundamentals
  2. Troubleshooting

Duplicate component paths

PreviousTroubleshootingNextOAuth 2.0

Last updated 4 months ago

Duplicate component paths

Reason: There are components with duplicate paths. Duplicate paths cause problems such as incorrect quantities or duplicate entries in the destination system and are therefore blocked on a UI level.

To illustrate, given an assembly with the following structure:

A1
→ P1
→ A2
 → P2
 → P3

You’ll have 4 entries in the SharpSync UI. These entries will all have a unique component path such as:

A1
A1/P1
A1/A2
A1/A2/P2
A1/A2/P3

A problem can arise if you use part numbers to generate the item. Let’s say you make a copy of P2 => P3, and you forget to update the part number. You have part numbers assigned as follows:

A1 → A1
P1 → P1
A2 → A2
P2 → P2
P3 → P2

Then the component paths generated will look like this

A1
A1/P1
A1/A2
A1/A2/P2  *
A1/A2/P2  *

The duplicate entries (bottom 2) are the ones causing the problem that you’re seeing onscreen with the error message. To resolve this, update the part number in the source system or change the way the data is being pulled. In some Data Source add-ins (such as Inventor and SolidWorks and SolidWorks PDM) you have the ability to pick either the filename or a custom property to use as the component name.