"Staff ID" not Populating in Catalog Item Due to "Variable Name Mismatch" in Azure IntegrationIssue Customers reported that when submitting a catalog item via integration with Azure, all fields display values correctly except the Staff ID. SymptomsStaff ID field remains blank after submission.Other fields (e.g., Name, Email, Department) populate successfully.Value for Staff ID is visible in the integration payload, but not reflected in the catalog item form.FactsThe variable for Staff ID in the catalog item is:<name>mab_staff_id_nric_passport_no</name>Azure payload is sending Staff ID with a different variable name than what ServiceNow expects."Show XML" review confirms the correct ServiceNow variable reference is mab_staff_id_nric_passport_noScreenshots from the customer show the mismatch in variable naming between ServiceNow and Azure parsing logic.ReleaseThis behavior is not release-specific and can occur in all ServiceNow versions when integration variable names do not match.CauseThe Staff ID is not populating because of a variable name mismatch between the catalog item configuration in ServiceNow and the JSON payload being sent from Azure. ServiceNow is expecting mab_staff_id_nric_passport_no, but the payload references a different name.ResolutionTo resolve this issue, please follow these steps: Review the ServiceNow catalog item variable name for Staff ID:Confirm that it is configured as mab_staff_id_nric_passport_no.Share this expected variable name with the Azure/third-party integration team.Request the integration team to update their parsing logic to use the correct variable name (mab_staff_id_nric_passport_no).Retest the catalog item submission after the update.Confirm that the Staff ID now populates correctly along with other fields. 💡 Tip: Always ensure variable names in the integration payload match the catalog item variable names in ServiceNow. Even small mismatches can result in data not being captured.