Details

    • Type: Bug
    • Status: To Do
    • Priority: Low
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Company:
      GEO

      Description

      Please find a new bus for DMS/GEO.

      Concern:
      • The mapped field seems to be pulling an invalid field not tied to the system field in CBAT

      Investigation: w
      • Our team have checked the candidate file, DMS doc, and requisition – all look good
      • 3min video showing error and troubleshooting: https://share.vidyard.com/watch/Pk2EQJXL6Ua6EUcpswHQXU?
      • Tested in another req and the data maps over correctly, expect the req the error.

        Attachments

          Activity

          Hide
          XavierL Xavier Laurent (Inactive) added a comment -

          I agree with Alexandre. The field we are looking to map to the document is the one on the Requisition (which should be single select); we mapped that field rather than the one on the candidate profile precisely for the reason that the one on the candidate profile could have multiple values (candidate applying to multiple req with different values, or candidate joining the talent network selecting multiple type of employment).

           

          I believe the issue here is the mapping between CBAT and DMS; the DMS mapping tag say: Requisition_Status_For_Job_Postings-Job Desired.Status for Job Postings – must match the populated field above.

           

          Could you update the mapping of this field between CBAT and DMS to map Requisition_Status_For_Job_Postings  to CBAT PropID=42 (not propID=118)

          Show
          XavierL Xavier Laurent (Inactive) added a comment - I agree with Alexandre. The field we are looking to map to the document is the one on the Requisition (which should be single select); we mapped that field rather than the one on the candidate profile precisely for the reason that the one on the candidate profile could have multiple values (candidate applying to multiple req with different values, or candidate joining the talent network selecting multiple type of employment).   I believe the issue here is the mapping between CBAT and DMS; the DMS mapping tag say: Requisition_Status_For_Job_Postings-Job Desired.Status for Job Postings – must match the populated field above.    Could you update the mapping of this field between CBAT and DMS to map Requisition_Status_For_Job_Postings  to CBAT PropID=42 (not propID=118)

            People

            Assignee:
            samir Samir
            Reporter:
            EricH Eric Hernandez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: