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
Currently there is only one "Name" field, and a "Readable plural name" field when setting up the name for a Custom Object Type.
If you choose a Name like "DNS Record", then the REST API endpoints automatically use "dns%20record" in them, which is kinda ugly.
It seems like it might be better to have a Name field that gets used for REST API, and a separate "Label" field that is used in the UI for display. And it might make sense to change the "Readable plural name" field to be referred to as "Readable plural label".
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Currently there is only one "Name" field, and a "Readable plural name" field when setting up the name for a Custom Object Type.
If you choose a Name like "DNS Record", then the REST API endpoints automatically use "dns%20record" in them, which is kinda ugly.
It seems like it might be better to have a Name field that gets used for REST API, and a separate "Label" field that is used in the UI for display. And it might make sense to change the "Readable plural name" field to be referred to as "Readable plural label".
Beta Was this translation helpful? Give feedback.
All reactions