Form Field Reuse Count Tool

Description

Optionally lowercase both field lists, deduplicate them and return shared fields in first-list encounter order and their count.

Administrative records depend on literal identifiers, numbering conventions, check alphabets and ownership mappings. A duplicate count, check symbol or one-hop route helps reconcile metadata without authenticating a document or establishing who has authority over it. A well-formed label can still refer to the wrong record.

Optionally lowercase both field lists, deduplicate them and return shared fields in first-list encounter order and their count.

When to use this tool

Use Form Field Reuse Count when checking the stated administrative key, numbering, continuity or routing convention.

How to use the tool and how it works

Enter firstFields, secondFields, caseSensitive. Follow any array-alignment requirements below. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read reusedCount, sharedFields. Use the output convention below.

Optionally lowercase both field lists, deduplicate them and return shared fields in first-list encounter order and their count.^[1]

Code points, UTF-16 code units, canonical decomposition and case conversion are different operations. This helper follows its explicit local convention rather than linguistic analysis or rendered-text measurement.^[2]

Input field	Meaning and units	Accepted input
firstFields	First Fields	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
secondFields	Second Fields	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
caseSensitive	Case Sensitive	Required. Boolean.

Output field	Interpretation	Returned shape
reusedCount	Reused Count	Required. Safe integer.
sharedFields	Shared Fields	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.

json

{
  "input": {
    "firstFields": [
      "Name",
      "Age",
      "Age"
    ],
    "secondFields": [
      "name",
      "City"
    ],
    "caseSensitive": false
  },
  "output": {
    "reusedCount": 1,
    "sharedFields": [
      "name"
    ]
  }
}

Limitations and assumptions

Case-insensitive mode uses full string lowercasing, not locale-aware matching, Unicode normalization or semantic field equivalence.
Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Use authoritative source records and the complete applicable document/process scheme for actual identity, routing or integrity decisions.

References

Calculation and input contract: administrative-science/form-field-reuse-count — tool.io
Unicode 17.0: encoding and normalization conventions — Unicode Consortium

Similar or alternative tools

Form Repeated Field Count
Return distinct literal field IDs and fieldIds.length-distinct count as repeated occurrences.
Form Source Key Ambiguity Gap
Group distinct source keys per target; count targets with multiple sources, distinct targets and distinctTargets-requiredTargetCount.