Actions
Bug #7436
closedUser import not importing field data
Description
Only core fields appear to be importing for some reason. Custom fields are not importing.
Updated by krileon almost 6 years ago
It's due to the empty user object not having the fields initialized so they don't exist with calling get_object_vars on the object.
Updated by krileon almost 6 years ago
I don't think this column check is even necessary. Just remove it.
Updated by krileon almost 6 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Fixed in MR !1451
Updated by krileon almost 6 years ago
- Status changed from Resolved to Assigned
- % Done changed from 100 to 80
The import will fail and error if it tries to import something that doesn't exist when in that case we'll just want to skip over that data.
Updated by krileon almost 6 years ago
- Status changed from Assigned to Resolved
- % Done changed from 80 to 100
Updated by krileon almost 6 years ago
Fixed by using current logged in user object to determine available columns when importing a new row.
Actions