You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i am digging into the silverpop api and have just learned about the update_if_found and sync_fields flag of the addrecipient command.
is this supported? they are telling us that using a non keyed database is preferable when combing sms and email into a single DB. In order to update an existing record I went the easy route and set the UPDATE_IF_FOUND flag to true. one of the dbs i was writing to had no unique key set up and i got an error saying i needed to use SYNC_FIELDS on databases with no unique key if the UPDATE_IF_FOUND flag is set.
Hi Jason, I don't have anyone available right now to add this, but we would certainly accept a pull request if you wanted to give it a try. It really wouldn't be complicated. You'd need a new SyncField class in the elements package modeled after the existing Column class, and then a new sync fields list instance variable in the AddRecipientCommand class using that new SyncField class. Then just setter/getter methods and I think that should do the trick.
HI,
i am digging into the silverpop api and have just learned about the update_if_found and sync_fields flag of the addrecipient command.
is this supported? they are telling us that using a non keyed database is preferable when combing sms and email into a single DB. In order to update an existing record I went the easy route and set the UPDATE_IF_FOUND flag to true. one of the dbs i was writing to had no unique key set up and i got an error saying i needed to use SYNC_FIELDS on databases with no unique key if the UPDATE_IF_FOUND flag is set.
i don't see support for that here https://github.com/Silverpop/engage-api-client/blob/master/src/main/java/com/silverpop/api/client/command/AddRecipientCommand.java
our support rep sent over the following
85628 2 EMAIL [email protected] Customer Id 123-45-6789 Email [email protected] ```
The text was updated successfully, but these errors were encountered: