Members are mapped based on the loginname since that should be unique anyway, therefore you don't need to enter key information since login is always the key. V3 comes with an option to delete records that no longer exists so you can delete the old ones but not finished yet.
Hmmm, thats a problem, because in my Website members are imported, but can login afterwards and choose to change their loginname.
I'm running an update routine every night, from an external Membership source. Thats why it is a problem.
Do you think its possible to work around this in an Event, I would have to switch the importing member object and discard the newly made one. Something like that..
No real event you can use the RecordImporting event to cancel the new imported record but the member is already created at that time.
What you could try, not sure if it works is to swap the member to the old member when it already exists and delete the newly created member. I think when you assign a new member object in the event the rest of the code will use that value as well. But that is something I have never tried before.
Member not updated but duplicated
Hi Richard,
It appears my member import is duplicating Members on the second import if I change the loginname after the first import.
how are the relations mapped? My CMSImportRelation Table (and all the orther relation tables) appears to be entirely empty.
Martin
Hi Martin,
Members are mapped based on the loginname since that should be unique anyway, therefore you don't need to enter key information since login is always the key. V3 comes with an option to delete records that no longer exists so you can delete the old ones but not finished yet.
Best,
Richard
Hmmm, thats a problem, because in my Website members are imported, but can login afterwards and choose to change their loginname.
I'm running an update routine every night, from an external Membership source. Thats why it is a problem.
Do you think its possible to work around this in an Event, I would have to switch the importing member object and discard the newly made one. Something like that..
Hi Martin,
No real event you can use the RecordImporting event to cancel the new imported record but the member is already created at that time.
What you could try, not sure if it works is to swap the member to the old member when it already exists and delete the newly created member. I think when you assign a new member object in the event the rest of the code will use that value as well. But that is something I have never tried before.
Hope that could help you.
Best,
Richard
Thanks for your quick answers.
I'll try adapting the Xml after its requested from the external Source and before its fed to cmsimport.
Thats a little easier I think.
Martin
Yup and less hacky... ;-)
is working on a reply...