Batch Update ""Display As"" Property
It is my understanding that you cannot use the QuickBase API to change a field's type. However, API_SetFieldProperties has been quite the time saver when working with large groups of similar fields. ...
Forum Discussion
The field name is the "Display As". I wish there was a different field for "Display As" that we can use for forms and reports, dynamic filters and so on, but alas, Quick Base doesn't have that yet. I have requested for this feature on User voice though.
I have no clue what you mean by "Display As" field property. Can you post a screenshot displaying this field property?
In regards to the API, it is a limitation to think that calling an API method (eg ?act=API_*) is any different that calling any URL method. With appropriate access, you can call any "native" URL method (eg ?a=er), or "internal" URL methods (eg ?a=QBI_*, ?a=JBI_*) as conveniently as calling any API method (eg ?act=API_*).
The only substantial distinction between an API method (eg ?act=API_*) and any other URL method is that QuickBase has published the API methods and implicitly will support them as published for the foreseeable future whereas the other URL methods may change over time. But the reality is these other URL methods don't change very frequently over time.
In regards to the API, it is a limitation to think that calling an API method (eg ?act=API_*) is any different that calling any URL method. With appropriate access, you can call any "native" URL method (eg ?a=er), or "internal" URL methods (eg ?a=QBI_*, ?a=JBI_*) as conveniently as calling any API method (eg ?act=API_*).
The only substantial distinction between an API method (eg ?act=API_*) and any other URL method is that QuickBase has published the API methods and implicitly will support them as published for the foreseeable future whereas the other URL methods may change over time. But the reality is these other URL methods don't change very frequently over time.