Previously, when using the fill-down feature in custom text columns, numeric values (e.g., 3) were incorrectly treated as numbers instead of text strings (e.g., "3"). This caused errors when saving data to the backend.

This bug has been fixed: numeric inputs in text fields are consistently handled as strings.