Description:
Our custom LocationHierarchy endpoint exhibits different behaviors when using different JPA servers. When hitting the endpoint in the production environment, the response includes the children block as expected. However, in the staging environment, the children block is missing from the response.

Production Response:

{
  "LocationHierarchyTree": {
    "locationsHierarchy": {
      "listOfNodes": {
        "treeNodeId": "Location/<locationId>",
        "treeNode": [
          {
            "nodeId": "Location/<locationId>",
            "label": "Some FHIR Location",
            "node": { ... },
            "children": [ ... ]
          }
        ]
      }
    }
  }
}

Stage Response:

{
  "LocationHierarchyTree": {
    "locationsHierarchy": {
      "listOfNodes": {
        "treeNodeId": "Location/<locationId>",
        "treeNode": [
          {
            "nodeId": "Location/<locationId>",
            "label": "Some FHIR Location",
            "node": { ... }
          }
        ]
      }
    }
  }
}

Note: The children block is missing in the stage response.

Investigation Findings:
The root cause of this inconsistency is the getId() function in the Location class. This function should return the ID of the location in the format Location/<locationId>. While this format is correctly returned in the production environment, in the stage environment, the ID is returned as a URL, such as "http://host-server:<port>/fhir/Location/<locationId>".

This discrepancy in the ID format is causing the children block to be omitted from the stage environment response.