Hello,

I purchased this module today and installed it with a very specific job to do. 

I did an export all of users in the portal with all fields selected in the export to a csv file.  This worked fine.

i then did an import of the same csv file, and the wizard was working fine.  It listed all the user profile properties including two custom ones i had inserted which were "birthmonth" and "anniversarydate".  it asked that I match them up with the fields in the dnn install, which i did in the dropdown menus.  So basically at this point I had an exact list of exported properties that matched the same names as the dropdown menus for every field.  it was a perfect match.. which was great.

I clicked the next button, and it enabled to setup a specific filter, of which I selected my custom profile attribute of "birthmonth" listed above with it equal to "November".  This particular attribute is simply a dropdown of months, so November is valid. This seemed to work fine.

I clicked next and it displayed an example of the import users and under the birthmonth and anniversarydate fields it had information from the profile like address, and zipcode.  in other words it did not list the profile information correctly and show the birthmonth and anniversary information.  I then expanded the Core area to see the list of fields that were being imported and what they related to in the DNN install and for birthmonth and anniversary date they both listed "telephone".  This was not good.

So my conclusion is that it is not picking up the custom profile fields correctly from the previous step in the wizard where for birthmonth I had selected birthmonth and not telephone, and for anniversarydate i selected anniversarydate and not telephone.  i clicked the previous button to try again, but received the same results.

It seems like if the fields are empty possibly it is messing with the import function.  Of all the thousands of users in the system probably only a few have selected the November option for birthmonth.

I need an answer very quickly to get this fixed.  Would it be better to not use CSV? and maybe use a different export file?

I tried exporting with a ; delimiter and a , delimiter but received the same results either way.

My objective is to export the full list of users, and then (in this case) filter out only users with "November" as the selected birthmonth and I will import them into a role i have created called "November Birth Months". This way I can send them a newsletter wishing them a happy birthday in November.

However the problem I am encountering above is not allowing me to get the correct values for this custom enter profile field of birthmonth. The same problem exists for anniversary date or any other custom profile field that exists in this DNN install.

Thanks
James

Ok, I went into the exported CSV file and do see that it exported incorrectly in that my custom profile fields were not organized correctly. It had my birthmonth under some other heading, and same with anniversary date, so there is an issue with the export collecting the custom profile fields correctly from dnn.

So I went ahead and put in some values in the CSV file for birthmonth and anniversarydate just on the first user record. I then went through the wizard and found when I got to the page that showed the list of users the first user that i inserted these fields was correctly displayed. It had the November, but the next user on the list had the next field value (which was address) written under BirthMonth. So this list of users is not reading when there is no value, and it just places the next field, which is a problem.

Lastly I expanded once again the Core area to see that for BirthMonth and Anniversary Date, both had telephone as the selected profile profile instead of the appropriate custom profile field selected earlier in the wizard.

There are definitely some issues here....

Thanks
James

Hi,

No, its still not right, after installing the patch you sent.  I followed the same steps and now when i get to the page that lists the demo users it has the address in the email column and email in the DisplayName column.  Everything is off some and this because the import I did probably didn't have any displaynames.. they were blank, so it pushes over the next field which is e-mail and displays that in the DisplayName column.  It is not recognizing when the fields are blank in the import.

Then I open Core Intregration on that page and it has for the custom fields:
BirthMonth = Telephone
AnniversaryDate = Telephone

Telphone = Telephone which is the last field it displays before the custom fields, so maybe it is just repeating it.

I sent an email with the information you need to go into our installation.

Thanks
James

James,

Hi. I just wanted to continue to follow up on this thread/issue here... After reviewing your site I found that although the module supports 2 and 3 digit property definition ID's it did not support property definition ID's that were 4 characters long... We applied a fix for this (and it does appear to have fixed setting and mapping these fields to the core fields) however we are still reviewing an issue during the actual import process.

We can continue to post but I wanted to update what information we had/have been reviewing.

Thanks,

Chad