Hello to all Interactive User Import/Export 3.0 users,
I have used this module on DNN4.8.4 extensively for my site launch last month and found out issues that were not mentioned in the User Guide. There are goods and bads depends on how you make use of them. I hope we can get a FREE upgrade to the next version which enhanced the followings.
1) IMPORTING (new) and OVERWRITING (existing) processes will turn accent characters into unknown characters. (yes a lot of users aware of this) I have to manually edit them afterwards which is painful.
2) Even including passwords field in the import file and check it to overwrite existing users, their existing password will never be overwritten. If there is an option to force-overwriting the password then it will be perfect.
3) Using IMPORT to create new users will only create the user accounts, BUT NOT authorizing these newly created users to login. The [Authorised] field of these newly created accounts in [UserPortals] table are still "False". So Mr. developer why not authorizing them at the first place? The work-around to turn their [Authorized] from False to True, you can import the same file again with "overwite existing record". It can be done without doing it manually or through SQL update statement.
4) I configured all users to change their passwords during their first login. By using this logic I can look at the [UpdatePassword] field in [Users] table and have an ideo of who have already tried using the site. However, by IMPORT process to update the exisitng user records, it will automatically turn all their [UpdatePassword] field to "False" (no password change is required). I was shocked! This overwriting action is totally UNTOLD and UNWANTED! Although I have backup to save me from being flied, pls give it as an option.
5) I had 3 import files. I added the first one to IMPORT schedule, then before it was executed I added the second and third files to the IMPORT schedule. So there should be 3 different import files in the IMPORT schedule. However, it turned out that it sticked to the first import file and executed 3 times. Since the first import file was processed 3 times, the users assigned in the first import file received the same email 3 times. That was embarrassing. Lesson learned from that - Never add another process before the previous was executed. What's more, to play safe, I always delete the temp CSV created in Portal folder before another IMPORT.
Cheers.
Eric  |