[SLPS]

Hello!

There are several ways to tackle what I need to do, I’m wondering which would be best. I will be exporting data from Active Directory to put into connections. This would be fine, except that our phone numbers are not in AD, they have to be manually input (which is the main reason we went with Connections). So ideally I’d want to not dump the database each time we import, but I need to match up the records on the email address, not the wordpress ID.

I can try to do custom coding to facilitate this (one of the other reasons we went with Connections is because of how you store the data).

So I’m left with this: Should I write external code to try to do this? Should I modify Connections to use email instead of ID? Will you be doing Rest soon and would I be able to add/update records that way? If so, how far off is that? Or is there some other method that I have not thought of? Thank you!!

• This topic was modified 5 years, 4 months ago by SLPS.

[Steven Zahm]

@ SLPS

The CSV Import extension could be modded to match on email instead of ID. You would have to edit the cnCSV::import() method, lines 262–267. You would query the email table to find a matching email address. The select would be the entry_id. You would use the returned value, if a match was found, to init the cnEntry object just as it is done within the current lines of code mentioned above. I would be open to adding a filter in which you could hook into so you could simply hook into it and return an entry object.

As for REST… I’ve put that on hold while I rework the internal a bit to make it easier to add/modify entry data such as addresses, phone and email. I’m moving to objects which helps breaking out the complex code in the entry object into smaller more manageable code.

Hope this helps, let me know.

[Author]

Posts