Well, I thought I had it all figured out with my review of the Bulk Import
Tool….specifically with regards to using the Bulk Import Tool to perform bulk edits of existing data.
Looks like I may have missed one key element.
Recently when trying to edit a group of existing projects, the tool kept returning an error of customfieldmaxvaluesexceeded. The weird thing was that the error wouldn’t occur on every project, but only some projects – and then not on the same projects in DEV and PROD.
After playing with a couple scenarios, I think that I’ve figured out the issue.
The Bulk Import Tool will return the customfieldmaxvaluesexceeded under the following circumstances:
- The user is attempting to edit a field connected to a lookup table.
- The field is already populated.
- The new value is different than the original value.
This issue will not occur when the new value is the same as the old value, or if the lookup value is blank before the edit.
I am still trying to identify a valid workaround, but for now, I might make the following recommendations:
- Manually edit those projects and clear out the lookup values. Although, of course, by the time you do that, you may as well have just set the values correctly.
- Export the data into Excel. Edit in Excel. Delete the old lookup field, create a new one, and then use the Bulk Import Tool to modify the new data set.
- A variant of topic #2, but instead of deleting the field wholesale, simply delete the original value from the lookup table list. This will blank the fields that contain that specific value.
All in all, I would say that #1 is probably the least work intensive approach to getting around this restriction.