> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/schindlerid/cardholder-management-interface/configuring-schindler-cardholders/mapping-schindler-badge-numbers/badge-number-conversion.md).

# Schindler Badge Number Conversion

Schindler Badge Number Conversion

The Badge Number PDF value entered will be imported into Schindler as the Schindler Badge Number.

Badge numbers can be converted from decimal format to hexadecimal format when imported into Schindler. In order to perform the conversion you will need to create the following registry entries and define the appropriate values for each:

<table><thead><tr><th width="183.111083984375">Registry Entry Name</th><th width="134.6666259765625">Type</th><th width="127.55560302734375">Value</th><th>Meaning</th></tr></thead><tbody><tr><td rowspan="3">BadgeNumberConvert</td><td rowspan="3">REG_DWORD</td><td>1</td><td>The conversion is performed and the BadgeNumberConstant is added to the front of the converted value of the Badge Number PDF value.</td></tr><tr><td>2</td><td>The conversion is performed and the BadgeNumberConstant is added to the end of the converted value of the Badge Number PDF value.</td></tr><tr><td>0/Other/Not present</td><td>The conversion is not performed.</td></tr><tr><td>BadgeNumberLength</td><td colspan="2">REG_DWORD</td><td>The length of the whole Badge Number once converted. The length cannot be more than the sum of 'HI' and 'LO' number of digits configured in Schindler, as configured in Schindler at <strong>Network, Elevators, Tools > 3rd party database interface</strong>.</td></tr><tr><td>BadgeNumberConstant</td><td colspan="2">REG_SZ</td><td>A constant in hexadecimal notation that is added to the front or end of every converted Badge Number.</td></tr></tbody></table>

#### Creating a registry entry

Perform the following procedure to create a registry entry:

**Note:** The registry entries will need to be created on each Command Centre workstation. If a registry value is changed, ensure all other workstation registry values are updated.

1. From the Start menu, click **Run...**
2. Type in 'regedit' and click **OK**. The **Registry Editor** opens.
3. Path your way to HKEY\_LOCAL\_MACHINE\SOFTWARE\GALLAGHER\Command Centre FT.

   **Note:** If using a 64 bit system, path you way to HKEY\_LOCAL\_MACHINE\SOFTWARE\Wow6432Node\GALLAGHER\Command Centre FT.
4. Right click, then click **New** from the drop-down menu. Another drop-down menu displays. Click **DWORD Value**. Your new DWORD Value is populated at the bottom of the registry values list.
5. Enter the DWORD Value name, (e.g. BadgeNumberConvert).
6. Double-click your newly created DWORD Value. The **Edit DWORD Value** window displays.
7. Select **Decimal** as the Base then enter your new value, (e.g. 1) and click **OK**.
8. Repeat this procedure to create the other registries.

#### Conversion conditions

To perform a successful conversion, ensure the following is correct:

* All three registry entries mentioned are present
* The 'BadgeNumberConvert' value is 1 or 2
* The Badge Number PDF value is a decimal number (0 - 4294967294)
* The length of the converted value plus the length of the 'BadgeNumberConstant' is less than or equal to the 'BadgeNumberLength'

When the number is converted into hexadecimal notation, leading zeros are added to the converted value so its length equals 'BadgeNumberLength'.

Badge Numbers that are successfully imported into Schindler can be found in Schindler at **Users/Building > Users** (select a user) **> Assigned ID media**.

**Note:** If the conversion is unsuccessful the card number is imported as is.

Conversion examples:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1a5b3a86480f0d34d1af62bd752928699eaf0c94%2Fschindler_badgenumberconversion.png?alt=media)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/schindlerid/cardholder-management-interface/configuring-schindler-cardholders/mapping-schindler-badge-numbers/badge-number-conversion.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
