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
In cases where Glide uses a column identifier instead of the user entered label for the column name property, the extension should take the column name from the property key i.e. in the example below it should parse out newColumnForDate as the label for the field in the popup input form. In an ideal world it would break that apart into "New Column for Date' but more challenging to convert it than to just use it as is. The unique column name is just not human friendly enough and doesn't show easily in the data editor to reference.
In cases where Glide uses a column identifier instead of the user entered label for the column name property, the extension should take the column name from the property key i.e. in the example below it should parse out
newColumnForDate
as the label for the field in the popup input form. In an ideal world it would break that apart into "New Column for Date' but more challenging to convert it than to just use it as is. The unique column name is just not human friendly enough and doesn't show easily in the data editor to reference.The text was updated successfully, but these errors were encountered: