You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Arches project version: 7.5.1
Web Browser: Chrome
Python version: 3.10
We have added an auto add of records when a new resource is created which is the Primary Reference Number. The automation is triggered from the database when a new resource is created in the front end.
Previously in 7.4.x, the Primary Key automatically shows as a descriptor when creating a new resource. However, in 7.5.1, that has some change.
As an example, User created a new Botanical Heritage resource which is BOT-1117. The Tutangi ID got generated automatically after her refreshing the resource, however, we did notice that the Display Name is still showing :
Looking through the Search Map, it also just shows as rather than the ID which could be an indexing issue.
However, after further investigation and troubleshooting, I think what is happening is because the Tutangi ID is automatically being generated from the database, it is not being saved using the ADD button. There might be a code in the ADD (SAVE) button in the front end that is calling an index code and updates the name in the resource or descriptions.
As a test, I updated BOT-1117 to BOT-1118 and click SAVE EDIT
Which has then updated the Display Name to show the Tutangi ID
NOTE: Also, might be related to this issue – reading through the 7.5.0 release notes, one of the breaking changes notes is about the descriptors:
The text was updated successfully, but these errors were encountered:
Arches project version: 7.5.1
Web Browser: Chrome
Python version: 3.10
We have added an auto add of records when a new resource is created which is the Primary Reference Number. The automation is triggered from the database when a new resource is created in the front end.
Previously in 7.4.x, the Primary Key automatically shows as a descriptor when creating a new resource. However, in 7.5.1, that has some change.
As an example, User created a new Botanical Heritage resource which is BOT-1117. The Tutangi ID got generated automatically after her refreshing the resource, however, we did notice that the Display Name is still showing :

Looking through the Search Map, it also just shows as rather than the ID which could be an indexing issue.

However, after further investigation and troubleshooting, I think what is happening is because the Tutangi ID is automatically being generated from the database, it is not being saved using the ADD button. There might be a code in the ADD (SAVE) button in the front end that is calling an index code and updates the name in the resource or descriptions.
As a test, I updated BOT-1117 to BOT-1118 and click SAVE EDIT


Which has then updated the Display Name to show the Tutangi ID
NOTE: Also, might be related to this issue – reading through the 7.5.0 release notes, one of the breaking changes notes is about the descriptors:

The text was updated successfully, but these errors were encountered: