While converting a particular account from individual to household from the NextGen desktop client (“Constituents>Household Operations>Convert to Household…”) the operation would fail silently (no error or pop up message) and won’t do the conversion though it was converting other individual accounts to household accounts without any issue. Then on further test, to check what was preventing this account from conversion but not others, we found that the individual account in question has an association with another account. Once that association was removed, the conversion happened without any problem. Does anyone know if it is an expected (/documented) application behavior and is there any way to change this behavior (from any system table)? Thanks for any insight.
Best,
Mo
The National Ballet of Canada
This is fixed in v11.0.3. Here is the release note, #2264:
Fixed a defect in the convert Individual to household function where the conversion would not happen if the individual had pre-existing associations.