`Cannot read properties of undefined (reading 'canAutoIncrement')` when opening any form

[grantfitzsimmons]

Introduced in #6710

Describe the bug
When the Catalog Number format is set to CatalogNumberString (one of our long-standing defaults) or nothing at all (empty CatalogNumFormatName in collection), Specify crashes immediately when opening a new data entry game:

Cannot read properties of undefined (reading 'canAutoIncrement')

If the Catalog Number is set to a non-external catalog number format or a custom one configured in UIFieldFormatters, it does not crash!

Does not happen in v7.11.0.2

To Reproduce
Steps to reproduce the behavior:

1. Use a database with CatalogNumberString (or an empty value) set as the CatalogNumFormatName in the collection or collectionobjecttype table.
2. See the crash immediately.

Expected behavior
Specify should handle empty catalog numbers or CatalogNumberString as a valid format (not enforcing validation).

Crash Report
Specify 7 Crash Report - 2025-07-18T19_37_24.948Z.txt

[grantfitzsimmons]

Seems it is related to the CatalogNumberString– it is being filtered out because of the <external>edu.ku.brc.specify.ui.CatalogNumberStringUIFieldFormatter</external> XML for the field formats. Since it doesn't recognize the format for the catalog number, it 💀

Updated issue description ^

[alesan99]

Note:
I messed up with these two lines 👇. There should be a check to make sure a formatter exists.
Of course ideally there should always be a catalog number formatter, but still in the worst case scenario this shouldn't cause an error.

specify7/specifyweb/frontend/js_src/lib/components/Forms/Save.tsx

Lines 260 to 261 in e6354e5

	const canAutoNumberFormatter = formatter.canAutoIncrement();
	const parser = formatterToParser(numberField, formatter);