Can we change the subclass of a Part from an import file?

We have several hundred Parts with the subclass ‘Standard Part’.  These are older parts that were originally added to Agile incorrectly.  We want to change each of them to a different subclass of ‘Product SKU’.  We can do this manually for each in the Web client.  When we hit the Edit button, it warns us that Page Three will be cleared.  This is fine and we continue.  The subclass changes and we are happy.  But doing this several hundred times by hand is not desirable.  We then built a csv file and tried the Import utility, selected Item, and it did allow us to map the subclass attribute.  When we hit Import, it fails with errors like:  
The type of ‘PART-1234’ cannot be changed since the object ‘PART-1234’ exist.
So, my question is, is there an automated way to accomplish this?

Add Comment
6 Answer(s)

Per the Import/Export User Guide, “For items in the import file that already exist in the target system, a type mismatch rejection error occurs if the default type assumed by import does not match the existing object in the target system.” So either the subclass in your import file is the default, or it will error out.

 If you want to convert all of the wrongly-typed “Standard Part” items to “Product SKU”, set “Product SKU” as the default subclass for Items in Import, run your file through and then change the setting back to what you would normally want. I am not 100% sure this will work, but I think it is worth a try.

Agile Angel Answered on April 11, 2019.
Add Comment

I got it to work with the Import tool by changing the preferences.  

Your csv file should look like this if you open it with Notepad.  In this example, all 3 parts currently have a subclass of ‘Standard Part’.  I am changing 2 of them to ‘Product ID’ and 1 to ‘Product SKU’.


5601013-012,Product ID

5601013-A,Product ID

5601013-A-E,Product SKU


Using the Import tool, click the Preferences button

Business Rule

Smart Rules Warning Violation Behavior: Reject Objects

Reference Designator Qty Mismatch Behavior: Reject

Behavior upon non-existing objects: Reject

Change Mode: Authoring

Default Types

Default Item class: Parts

Default Part type: Product SKU    — this may not be necessary to change, but it worked for me


Hit Save to save the preferences.   Hit Next.   Choose Item only.   Hit Next.


Data Mapping:     ( o )  Define attribute mapping in next step

Data Transformation:    ( o )  No transformations are necessary

Redline Options:    ( o )  Updates do not require redlining


Hit Next.

For the mapping

Part       –>  Parts > Title Block > Number

Part_Type  –>  Parts > Title Block > Part Type


Hit Next and then Import

Agile Talent Answered on April 11, 2019.
Add Comment

Keep in mind that once I hit that Import button, every attribute on Page Three will be wiped out and deleted for each of those parts being updated.  So, I am going to extract the PAGE_THREE table for these parts first and save to a file before I do the Import.

Agile Talent Answered on April 11, 2019.
Add Comment

Sorry folks.  But the above answer is INCORRECT.  My test was successful because another user logged in to Agile and converted my 3 test parts BEFORE I ran my test import file.  So, the subclass matched what they had changed it to earlier in the day.  My next test FAILED.   So, I guess we will need to convert each manually in the web client.

Agile Talent Answered on April 11, 2019.
Add Comment


 Other option is to develop a SDK process to do this (disabling all the warnings)

– Raj

Agile Expert Answered on April 11, 2019.
Add Comment

Using  Import functionality we cannot change item type.  Write few lines of SDK to change item type .

Agile User Answered on April 11, 2019.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.