In working on our V11 upgrade, we have decided to leave our logins on the individual accounts. I understand if an individual is affiliated to a household, the transactions made will move to the affiliated household account.
Does anyone know, if this individual changes any information, particularly their email address or contact permissions - does this update the individual account OR would this be added to the household account?
So the question is, when you log in are you in your individual account, or in your household account (or if it changes during the session at what point does this happen)?
Any info would be appreciated!
Hi Lisa
We are doing the same and leaving the logins on the individual rather than the household accounts. There are a couple of settings that appear in T_DEFAULTs that can control where the transactions appear but I'm not sure how these affect updates of addresses. I can tell you what we have been testing and are planning to use.
We have made the decision to keep all transactions at the individual level and like I said above any customer logins at individual level. So we have set the Transact_As_Household_Web to No.
We have found out through our testing this means that when you try to update customer contact information that you can run in to problems if there is no primary address information attached to that affiliate. We have to introduce the Web API method Shift_Context to move the locaction where contact information is stored.
This method basically controls which CONST_ID is used for that part web API for households. So you can shift context down on to the Affiliates or Shift Context on to the Household. So pretty powerful but does mean that you have to have some change to your web code.
Thanks
Nick
Hi Lisa,
In the case you are describing, the only individual data that can be updated is the name for the A1 and A2 records affiliated with the household. To update the individual’s email or contact permissions you would need to update your web code to use the new ShiftContext API method. You can read about v11 changes to the API in the SOAP API Guide. At the beginning of the document there is a section explaining changes related to the new constituent model.
Kevin Sheehan
Senior Documentation & Learning Resources Specialist
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
So does this mean that without implementing "ShiftContext" users would only be able to login as the household? and all changes made would apply to the household as well as all individuals within the household?
That's pretty much correct. Without making changes to your site to use ShiftContext when an individual logs in it switches to the household record and any changes you make will be to the household record not the individual record.