Configuration Import

Menu > Configuration Import

The Configuration Import should be used to update existing Part file data that is stored in R+. It can also be used to update any Part data regardless of its Site Admin Import setting, which is a helpful tool in a test environment.

This import type only allows you to update data, not replace it. However, it is not limited by Import Global Settings list, and you can update any field using this import type. This makes it the optimal and easiest import type for adding bulk updates of Part data.

circle-info

The Configuration Import can be used to update ANY part field - including part data that is typically imported via the interface (i.e. a field that is checked in the Import Global Settings).

If there is an accidental override of interfaced data, the next interface will override/update the checked field again with the correct data.

Formatting a CSV for a Configuration Import

When using a Configuration Import, it is best practice to trim the file to just the fields and part numbers that you wish to update. This prevents any other data from being accidentally overwritten.

There are also three mandatory fields that must be included with each Part file import: PartNumber, Revision, Location. These three fields make up the internal PartID in R+. Without them, R+ will not be able to recognize the part in the file, and will cause an error.

Example:

If you store Order Cycle values in R+ - not in your ERP - and it is time to update them using the Configuration Import, your import file would look like this:

In this example, you have removed all fields/columns that are not updating, and you have also only included those parts that you have made changes to. You have left in the three mandatory fields as well.

circle-info

Only trim an import file for a Configuration Import. The Configuration Import will only update the fields that exist in the file and does not require all columns for a successful upload. Do not trim the file if you are using a System Import. The System Import requires all columns to exist in the file for a successful upload.

Last updated

Was this helpful?