Table format for Locality not respected

[grantfitzsimmons]

Describe the bug
The table format configured in Specify 6 for Locality is not respected in Specify 7.

To Reproduce
Steps to reproduce the behavior:

1. Configure a table format for locality in 6.
2. See in 7.

Expected behavior
Table format should be the same in 6 and 7.

Screenshots

From CSIRO:

Desktop:

• OS: Windows 10
• Browser: Edge
• Specify 7 Version: 7.6.1

Reported By
CSIRO

[grantfitzsimmons]

May be related to #1144

[maxpatiiuk]

Is that the case for all tables?
Is that the case in the query builder?

[maxpatiiuk]

Unable to replicate when looking at the exact same record. This could have been a bug that have since been fixed in Specify 7.7.0

@grantfitzsimmons Can you please test this again? And if it happens, provide a URL to the record.

[benanhalt]

The query combo box defines it's own format. I think it uses the default format for the table if none is defined. And I think there can be different formats for what is in the results drop down vs when it is displaying the current selection.

[grantfitzsimmons]

Sorry, I am still not understanding why there is a discrepancy between Specify 6 and 7 here. The QCBX format defined in Specify should apply to both versions right?

[benanhalt]

Yes. Is the discrepancy still present in the current version?

[grantfitzsimmons]

Format for the query builder is using the system default but the query combo box is using the customized formatter.

db: ANFC

[benanhalt]

I created a new issue #2270 for the above since it has to do with the query builder results and may be separate from this issue.

[benanhalt]

It seems like that bug also affects the query cbx. When searching you see the results formatted as they are in the query builder results, and when you select one, it appears in that format in the unsaved form. The fix for that bug should resolve both.