I have an empty table that I changed the name of a single record. Upon saving it stated that I was going to change 61 items. The single record didn't share a name on any other table. Curious to know what is was attempting to change.
-
170 Points
Posted 5 months ago
Evan Martinez, Community Manager
-
10,354 Points
HI Scott,
How were you changing the name of that record? Were you updating it in the form for that record or were you using another method to change its name?
How were you changing the name of that record? Were you updating it in the form for that record or were you using another method to change its name?
-
170 Points
On the table I I went to settings and edited the field under the "a single record is called..."
Evan Martinez, Community Manager
-
10,354 Points
If this record or table was related to any other tables or displays in other places that warning message was letting you know everywhere in the product the name of individual records would be updated. So there was 61 places where the name of records in that table was referenced in your application in the schema.
Evan Martinez, Community Manager
-
10,354 Points
Hi Scott,
Then those changes should just be related to places in the application as a whole where the table was referenced outside of itself. Whether that be through reporting, dashboards, etc. It is referencing changes happening to the schema if it is using a message like the one below:
Then those changes should just be related to places in the application as a whole where the table was referenced outside of itself. Whether that be through reporting, dashboards, etc. It is referencing changes happening to the schema if it is using a message like the one below:
You have changed the terms used for records in this table from 'Documents' and 'Documentses' to 'Document' and 'Documents'. The terms 'Documents' and 'Documentses' appear in 1 place in this application. Would you like to replace 'Documents' and 'Documentses' with 'Document' and 'Documents' throughout your application?This warning is meant to help make admins aware that changing the table name or individual record term can cascade to other places in the application.
-
170 Points
Thanks for the note. That was the warning I received. It sounds like what you are stating is that in this case it's only a suggestion and the 61 places that my warning produced wouldn't be effected since there are no cross relations in this table.
Related Categories
-
Tables & fields
- 7109 Conversations
- 162 Followers