Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au

Skip to end of banner
Go to start of banner

TAP-982 Former Names and Trade As Names

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

How did we migrate the Old Names from Advance.

For Household Contacts, former names were migrated to AQB__Names__c object with type “Legacy system Former Name”

there were about 36,302 record migrated.

select id, AQB__ContactId__r.AQB__Deceased__c, AQB__ContactId__r.Account.RecordType.name from AQB__Names__c where AQB__Type__c = 'Legacy System Former Name'

For Organization Accounts, former names were not migrate to AQB__AccountNames__c as the practice in Advance was to duplicate the Account to represent a new name. As per Yeng, there was no deduplication done when we migrated those Accounts.

What are the possible ways we can represent a former name or Trade As Name of an Account?

Trade As Name where it has been created as a different account for receipting purposes, we should be able to merge the accounts to one and have the Receipting concern solutioned accordingly.

Method

Pointers

sample

1

Create a new account
Then subsequently create a linked Account to Account relationship that links the two accounts with current and former name or Legal and Trade As Name

  • Gifts Entry : Two account records. Old gifts can be in the old account, new gifts can be in the new account

  • Relationship Tree : By linking the two accounts, this appear in Relationship Tree. User can forget to link the two accounts or make the incorrect relationship type

  • Accounts : you need to flag the old account so that it will not be used anymore for correspondence or any transaction

  • Alternate Account name : not used

  • Contacts : you need to transfer the contacts to the new account and this makes the old Account orphaned.

  • Receipts :

  • Use this for when you need to keep record of or

  • Existing Records : review if the relationship is former name / Trade as Name. Consider migrating the former name to Alternate Name, then merge the two accounts together.

there are about 1,269 org account to org account relationship that needs to be reviewed.

select id,RecordType.Name, AQB__AccountId__r.name, AQB__AccountRole__r.name, AQB__RelatedAccount__r.name, AQB__RelatedAccountRole__r.name from AQB__RelationshipAccount__c where AQB__AccountId__r.RecordType.name != 'Household' and AQB__RelatedAccount__r.RecordType.name != 'Household' and RecordType.name != 'Non-Linked Account'

2

On the same Account record, Change the Account Name where this is logged in AccountHistory
Then subsequently create a non-Linked Account to Account relationship that links the two accounts

  • By creating the non-linked A2A relationship, this appear in Relationship Tree

  • you can record gifts just from the Account

There are only 6 records

select id,RecordType.Name, AQB__AccountId__r.name, AQB__AccountRole__r.name, AQB__RelatedAccount__r.name, AQB__RelatedAccountRole__r.name from AQB__RelationshipAccount__c where AQB__AccountId__r.RecordType.name != 'Household' and AQB__RelatedAccount__r.RecordType.name != 'Household' and RecordType.name = 'Non-Linked Account'

3

Use Alternate Account Name object that is linked to the Account to store the former/old name 👍

Recommended by AQ, also being used by Carnegie Mellon University

  • Gifts Entry : same account

  • Relationship Tree : will not reflect in relationship tree, but have the option to create a non linked account if so desired.

  • Accounts : Account is renamed to its legal name

  • Alternate Account name : will contain records of former name

  • Contacts : use the same contacts

  • Receipts :

  • this option records all the gifts and transactions of the one legal entity in one account regardless if the gift was given through a former name or a trade as name

  • Existing Records : review if valid

There are only 17 records

select id, AQB__Type__c, AQB__AccountId__r.Name from AQB__AccountNames__c

  • No labels