Testing 2021.R6 - Update the Employee Import to process the Employee

As a system processing the employee import I want the PersonId to populate the new OperatorId column in tbUser

Notes

• PersonId is used today, when the user being created is an Operator, to create the Master Level and assign the Operator to that level.
  • The XSLT's for both Operator ALL and Operator INCR already have this in them:

  •         <xsl:attribute name="PersonID">
              <xsl:value-of select="identity:Identification/identity:PersonID"/>
            </xsl:attribute>
    

• Going forward this section will be added to all Employee Import XSLTs
  • When the Audience is Operator, a Master Level will be created and maintained
  • For all file types, including Operator files, the PersonID will be used to provide a unique number to the user in tbUser

Acceptance Criteria

1. Confirm that the OperatorId requires a unique value
   • if two records are sent with the same PersonId, the second should be rejected/skipped and the file should continue processing
   • confirm that this duplicate exception is logged
2. Confirm that the format of the field is an Integer
   • Confirm that if a non integer value is sent, the record is rejected/skipped and the file continues processing
   • confirm that this non integer exception is logged
3. Confirm that the XSLT is updated the reflect the new field
4. There are a few different types of file are processed, and all should be tested:
   • Weekly - ALL files
     • Contractor_all
     • LimitedFE_all
     • InterimManager_all
     • Operator_all
     • Staff_all
     • TeamMember_all
   • Daily - Incremental Files
     • Contractor_incr
     • LimitedFE_incr
     • InterimManager_incr
     • Operator_incr
     • Staff_incr
     • TeamMember_incr
5. Validations:
   • If PersonId is Null in db, insert value from file
     • Confirm that the value is unique, if it is a duplicate, do not insert, and log a validation error
   • If PersonId is populated in db, and the same in the file, do nothing
   • If PersonId is populated in the db, but in the file, it is different, log a validation error

Notes: 8/24

• Multi site users. It is possible for the same user to work at two different stores, with the same guid and person id
• 
• However, only one user record is created in tbUser, and multiple records are created in tbEnityUser

  select * from tbuser with(nolock)
  where UserName = 'aaron.harges1'
  
  select * from tbEntityUser with(nolock)
  where UserID = 785851
  

Contact Will Englefieldfor the latest set of files, to process from Prod, to build out the data set. We must scrub the records after loading them.