Today’s tip is to combine two features of PLM 360 to make updating workspace data a snap. Use the reporting feature to create an Excel sheet on the existing information in a workspace, make the changes required, then import back into PLM 360.
For example, let’s say you want to add product line information to your Items and BOMs workspace. You have a list of values for the valid choices in another system, and will use a picklist to control these in PLM 360. Add the new field to your workspace then export key data to Excel (whatever fields you need to identify the record individually – if there’s an autonumber or a field that has a unique validator these are good candidates).
Creating the report will ensure the data is in the proper format for importing – you can use Excel to map the data from the other system. In our report, I just did Number as this is a unique field in the workspace.
One of the main reasons for this tip is a reminder to delete those first 3 rows before you try to import this back into PLM 360 (and be sure to save as file type .xls). In my Excel sheet, I’ll add the Product Line information and create a new import project (notice how I use the ‘match on’ on my key field).
I highlighted a bit at the bottom that’s particularly important here. You to specify what you want to do with picklist values. When I’m importing into a workspace with a picklist, I first select ‘error’ on ‘For new picklist values’ so that I can sanity check my spreadsheet and correct any typos. If you have lots of new values that will be coming in, you can just say ‘add to existing picklist’ and not have to do any picklist management if they are valid additions to the picklist.
Back to our example. See how the value for Product Line in the spreadsheet doesn’t match the picklist? This gives me a visual clue that I need to correct the value before importing if I want to use existing values only or I can add it to the picklist if I think it’s a valid choice.