1. Current Logic: TAWL – > SSHA Database – > Salesforce (Yardi is replacing TAWL)

  2. Current Delta logic for daily records:
  3. Yardi is replacing TAWL, but provide same steps

    3.1 What's changed in Yardi in data

    1) Telephone format:     


    		old formatnew format
    no ext4162345678(416) 234-5678
    ext41623456782202(416) 234-5678x2202

    2) Field (column) property changed


    		New Field featureOld Field feature
    Data Type for Household idString (varchar)number (int)
    Column property updated

    [Household Ref#] [varchar](10) ,

    [Member ID] [int] ,

    [First Name] [varchar](50) ,

    [Last Name] [varchar](50) ,

    [Gender] [varchar](6) ,

    [Date Of Birth] [date] ,


    [Application Current Status Code] [varchar](10) ,

    [Member Mailing Address Unit Number] [varchar](100) ,

    [Member Mailing Address Street Number] [varchar](100) ,

    [Member Mailing Address Text] [varchar](100) ,

    [Member Mailing Address City] [varchar](30) ,

    [Member Mailing Address Province] [varchar](2) ,

    [Member Mailing Address Postal Code] [varchar](7) ,

    [Home Phone] [varchar](32) ,

    [Mobile Phone] [varchar](32) ,

    [Bus Phone] [varchar](32) ,

    [Member eMail address] [varchar](80) ,

    [member_ref] [int] ,

    [LastUpdate] [datetime]

    Household Ref# bigint

    Member ID int

    First Name varchar 50

    Last Name varchar 50

    Gender varchar 6

    Date Of Birth date

    Application Create Date datetime

    Application Current Status Code varchar 6

    Member Mailing Address Unit Number varchar 10

    Member Mailing Address Street Number varchar 15

    Member Mailing Address Text varchar 80

    Member Mailing Address City varchar 30

    Member Mailing Address Province varchar 80

    Member Mailing Address Postal Code varchar 10

    Home Phone varchar 20

    Mobile Phone varchar 20

    Bus Phone varchar 20

    Member eMail address varchar 255

    member_ref int

    LastUpdate datetime

    3) Field name changed:

    YardiVisible in YardiTAWLVisible in TawlVisible in CRMMappingLabelDescription
    Applicant_Code
    (p-code)    		Yes


    		RGI_Applicant_Code__c
    		ID for describe a family


    		Household Ref#YesYesRGI_Houshold_Id__c
    		ID for describe a family
    Member_CodeYesMember IDNoNo
    SSHA_id__c
    		 -Family Member ID
    no this id
    		Applicant IDYesYesRGI_Member_Id__cRGI Application ID

    Requestor ID (Member_ref in table)
    For be compatible with TAWL, SSHA IT will keep 
    [Member ID] & [Applicant ID] mapping in its own database.


    4) Logic changed:
        – Member's ID in a family will be changed when the member is separated from the family.

    Concern: what's the change in Yardi (status??) and what impact in CRM. If Yardi mark the old member record as inactive, hsi datasync logic will take it as "Delete" and new member just as new added.

    -- Applicant ID can't be searchable in CRM:
       Current search in TAWL, household id and applicant id can be applied from UI. Also works in CRM UI.
       But Yardi doesn't have an applicant id, applicant id will be useless in CRM. 

    Concern: If confirmation from Yardi, the member id is same with current member id in TAWL, we can set Member id visible in CRM.