The header in the CSV file does not match the expected headers. Use the GetCSVHeader API to get the expected headers. about cognito-migrator HOT 9 CLOSED

Hey @rocker1058, thanks for raising the issue.

Can I ask a quick question - do any of your users have a value in the custom:client attribute?

I'm just about to deploy a new version which I'm hoping resolves this.

from cognito-migrator.

Hey @rocker1058, thanks for raising the issue.

Can I ask a quick question - do any of your users have a value in the custom:client attribute?

I'm just about to deploy a new version which I'm hoping resolves this.

yes, there are some users who have it, others who don't, this is an example of the attribute

custom:clients: [{"id":12923,"identificationNumber":"860828282","name":"3M COB."}]

I get this error:

Extracted custom attributes: custom:databaseUserId,custom:roles,custom:clients
Found user pool
[
{
"code": "invalid_type",
"expected": "string",
"received": "undefined",
"path": [
"custom:clients"
],
"message": "Required"
}
]
No users found

from cognito-migrator.

@rocker1058 can you try the latest release please (1.2.10)? That should resolve this and hopefully the original issue too :)

from cognito-migrator.

Actually, I don't think that will work either. Pushing a new version now!

from cognito-migrator.

Alright, give that a go! 1.2.11 should work now

from cognito-migrator.

Alright, give that a go! 1.2.11 should work now

The export works correctly with the custom attributes, but I got another error when importing.

The job says it failed because many users had an error:

[FAILED] Line Number 2 - Username should be an email ..
[FAILED] Line Number 3 - Username should be an email ..

This same thing happens for 50 users.

but it seems strange to me that you request that, I'm also going to ask aws support to get a response from them

from cognito-migrator.

[FAILED] Line Number 2 - Username should be an email ..
[FAILED] Line Number 3 - Username should be an email ..

I think that's a Cognito thing - the importer is only verifying that the fields are strings. I'm guessing there's a settings in the User Pool config.

from cognito-migrator.

It's worth saying that the exporter is setting "cognito:username": user.Username when exporting. I wonder if that needs to change depending on how the user pool is configured.

Do you have IDs in your Username field or email addresses?

In the docs it states:

The cognito:username field is required and must be unique within your user pool. It can be any Unicode string. However, it cannot contain spaces or tabs.

from cognito-migrator.

It's worth saying that the exporter is setting "cognito:username": user.Username when exporting. I wonder if that needs to change depending on how the user pool is configured.

Do you have IDs in your Username field or email addresses?

In the docs it states:

The cognito:username field is required and must be unique within your user pool. It can be any Unicode string. However, it cannot contain spaces or tabs.

I have ids

cognito:username: 04789468-f071-70c1-99e0-fdc60e0c6b57,

the email is only in the field "email"

from cognito-migrator.