Our software developers are trying to get the newsletter sign-up functionality working without forcing the customer to register, but have struck a problem with one of the Tessitura methods which is not behaving as they expect it should.
The basic problem is that we are creating a non-login constituent account, and then wish to update the constituent interests for that account. To do this, we’re taking the customer number which is returned when calling the “AddConstituent” method, and attempting to login to that account using the “LoginEx” method. The “LoginEx” method accepts customer number, phone and postcode as a valid combination for logging in – but for some reason this does not work for us.
If we’re able to login using the newly created account, we’d use the “UpdateConstituentInterests” method to update the details.
If anyone has any suggestions to help us resolve this problem please let us know.Thanks
Jeanette
you must create an account that in turn has a login and password before you can make the update constituent call. It's just the way it works.
I understand why you want to avoid that. Why do you make someone go through the trouble of creating a record when all they want is to sign up for your newsletter.
We compromised by putting a form that performs a register and then updateaccount, and update constituent intersts seemlessly to the customer, although they have to give us all the data. In other words, it is 1 form that does 3 things instead of breaking it down into 3 steps.