Error when editing taxon tree in specify7

Get Help
7

Hi Sylvie!

I’m sorry to hear the solution did not work for you.

Thankfully, we may be able to offer some further assistance.
The formatters for a field are defined in the UIFormatters App Resource.

If you need a refresher on App Resources in Specify 7, take a look at our documentation on the topic!
App Resources in Specify 7

In Specify 7, can you check the Field Format definition in the UIFormatters App Resource in the Discipline Resources?

The format causing the error is defined as the following:

<format system="false" name="VIROT_idtax" class="edu.ku.brc.specify.datamodel.Taxon" fieldname="commonName">
    <autonumber>edu.ku.brc.af.core.db.AutoNumberGeneric</autonumber>
    <field type="constant" size="3" value="TAX"/>
    <field type="separator" size="1" value="-"/>
    <field type="numeric" size="5" inc="true"/>
</format>

After editing the Field Format in Specify 6 and unchecking the ‘Is Incrementer’ checkbox, the formatter should have been updated to the following:

  <format system="false" name="VIROT_idtax" class="edu.ku.brc.specify.datamodel.Taxon" fieldname="commonName" default="true">
    <field type="constant" size="3" value="TAX"/>
    <field type="separator" size="1" value="-"/>
    <field type="numeric" size="5"/>
  </format>

Can you verify that this is the case?
If it is not the case, then can you try manually editing the UIFormatters in Specify 7 and replacing the prior VIROT_idtax format with the one provided above?

The below formatter is also equivalent and should work as well:

<format system="false" name="VIROT_idtax" class="edu.ku.brc.specify.datamodel.Taxon" fieldname="commonName">
    <autonumber>edu.ku.brc.af.core.db.AutoNumberGeneric</autonumber>
    <field type="constant" size="3" value="TAX"/>
    <field type="separator" size="1" value="-"/>
    <field type="numeric" size="5" inc="false"/>
</format>

:warning: After making these changes and saving the App Resource, please log out of Specify 7 and log back in. This is to ensure that Specify is not using the previously cached (stored) UIFormatters

If the formatter has been properly updated by Specify 6 and the error is still reproducible, then further investigation may be necessary and providing the previous backup of the database would be greatly appreciated!

Please reach out if you have any further questions or require clarification!

1 Like