When we import a file with columns that the system doesn’t recognise, it seems to put the values in the wrong columns.
For example – column headers are: (using commas for readabililty)
@user_login,user_password,custom1,custom2,roles,groups,meta:nickname
Values are
john,john123,CustomValue1,CustomValue2,subscriber,Group1,Johnny
What seems to happen is the “custom1” and “custom2” headings are ignored and so “CustomValue1” is imported as the role.
We’ve fixed it by removing those columns but if this is not just me doing something daft, then it’s worth documenting that it does this, I think.
Hi John,
Welcome to our support forum.
That’s correct, the columns names you used are not recognised by the system as described in the documentation so the wrong values are imported. This requires additional caution especially if you accidentally run the import and should always keep in mind the supported columns as indicated above.
However, I wouldn’t disagree with your idea, perhaps an additional note to alert other users would be useful.
Many thanks, note taken!
Kind regards,
George