Import Issues

Another issue is that it seems quite happy to create duplicate entries. I have discovered many members have multiple entries with the same details, all connected up to the same user. Probably created as a result of my import testing.

It took me a while to realize that my import issues were all to do with case sensitivity of plan names and field titles. This wasn't helped by the fact that a someone else was building the data and not being consistent.

I would like the import to fail if
- A plan is specified but it does not match an existing plan
- the entry is a duplicate

Hi Nick

At the moment, the extension doesn't prevent duplicate record. So before running the import, you should delete old subscription records (I can improve the import script so that it will prevent duplicate records, however, it will take time, about two weeks to have it implemented)

Tuan

Thank you Tuan, at least I know now.

My problem is that I have 2000 entries and every month I am importing additional subscribers so I can't just delete all subscribers before I import.

Our problem is that our existing membership system is the 'Master' database and so subscriptions are initially made there, at least for the time being.
At the risk of a separate question can an email be triggered when a user updates their profile?

In US we cannot save csv as yyyy/mm/dd format. Can you allow options more universal like mm/dd/yyyy?