I have a CSV with a header and two data records - one is a new user, the second is a exiting one to be updated. I check for the UserID>0 and set the userprofile to the userID else to -1 (if it doesn't exist). I then set other profile properties. On the save I get this error returned:

Username already exists, or password is not long enough for creating a new user. = '' = False

Although I get the error on both saves, the existing user fields are updated properly. Any ideas? The password is longer than 7 and the username for the new one doesn't exist.

Is the "Save" keyword also used for existing users (rather something like update?)

Below are the actions:

# Assignment: Assign <UserInfo> variable to 'Save,myNewContactID'.
# 40. If [myNewContactID.Error,Action] = ''
# 41. Execute Query[UpdateSuccess]: Update Lynx_ImportTest set etc...
# 42. Else
# 43. Execute Query[UpdateError]: etc.
# 44. Else

Click the ADD REPLY button and attach your configuration in an XML file. It's kind of hard to determine problems with the limited information. If I had to guess, #40 will NEVER equal true because you don't have single quotes around your left condition. It should be

If '[myNewContactID.Error,Action]' = ''

Also, make sure there are not other required fields that are not present on your UserInfo object. DNN make not like that.
Thanks,

I've enclosed the module export and csv file. You were right on using the ' - now the exiting user get updated without an error but new users don't. I set to -1, added PortID, UserName, email and Password. The save error comes back as '' but it creates user -1. Here's the debug:

+ If '[vUserID,SelectImport]' = '0'
# '0' = '0' = True
# Passed: Handling child actions.
# Executing
# Assignment: Assign <UserInfo> variable to '-1'.
* Executing
# Assignment: Assign <UserInfo> variable 'PortalID' to '[Portalid,System]'.
* Executing
* Assigned UserInfo (PortalID)
* Assigned Property (PortalID)
# Assignment: Assign <UserInfo> variable 'UserName' to '[vUserName,SelectImport]'.
* Executing
* Assigned Property (UserName)
# Assignment: Assign <UserInfo> variable 'Email' to '[vEmail,SelectImport]'.
* Executing
* Assigned UserInfo (Email)
* Assigned Membership (Email)
* Assigned Property (Email)
# Assignment: Assign <UserInfo> variable 'Password' to '[vPassword,SelectImport]'.
* Executing
* Assigned Membership (Password)
* Assigned Property (Password)
# Assignment: Assign <UserInfo> variable to 'Save,myNewContactID'.
* Executing
* Creating User
* Created User -1
# If '[MyNewContactID.Error,Action]' <> ''
* '' <> '' = False
* Failed: Skipping child actions.

Hi,

I think you should also be setting the DisplayName property for the <UserInfo> object. Usually, we set the dsipaly name to be their the userame or the combination of firstname and lastname. After a user is created, the user id can be access using [mynewContactID,Action] (action variable specified after Save).

Let us know if you encounter any more issues.

Thanks,
Sindura
R2integrated