Create, update, and troubleshoot object properties in Sanka.
Last updated: May 29, 2026
Properties are the fields that store information on Sanka records. Use properties to track values such as SKU, category, owner, status, delivery date, invoice number, or any custom data your team needs on an object.This guide explains what properties control, how to add them to records and forms, and what to check before changing a property that may be used by imports, reports, workflows, integrations, or AI.
What properties control
A property controls how a value is entered, stored, displayed, filtered, imported, and used in automations.Common property settings include:
Name: the label users see on records, forms, views, imports, exports, reports, and actions
Type: the input format, such as text, number, date, option, grouped option, conditional option, tag, or long text
Required field: whether users must enter a value before saving the record
Unique value: whether two records can share the same value
Option label and value: the displayed option name and the stable value used for matching and imports
Form and view placement: whether users can see or enter the property on a specific screen
Changing a property can affect record creation, CSV imports, reports, dashboards, workflows, integrations, and AI-assisted updates. If a field is missing from a screen, first check whether the property exists and whether it has been added to the relevant form or view.
Review a property change with AI
Ask AI to review the impact before adding, renaming, deleting, or changing a property that already appears in records or operations.
Sample prompt
/sanka Review this Sanka property change before making it. Show the object, property name, type, required setting, unique setting, option values, forms, views, imports, reports, workflows, integrations, and records that may be affected. Do not create, update, or delete the property yet.
After the review, confirm whether the change is safe to make now, should be tested on a small set of records first, or should be handled as a migration plan.
Create a property
From the left side of Sanka, open Workspace and select Object Management.
Select the object where you want to add the property.
In this example, select Item to open the Item property settings page.
Click New on the right side of the property settings.
Enter the property details. Turn on Required field only when every new record must have the value.
Enter a clear property name, then choose the property type.
For an option property, add labels and values. Labels are shown to users. Values are stable identifiers used for matching, imports, and consistency, so choose values carefully.
Click Create.
The property appears in the property list.
Add the property to the relevant forms and views so users can enter it and see it in record lists.
Use Text for short values such as codes, names, identifiers, and short notes. Use Text area for longer descriptions.Use unique values for fields such as SKU, external ID, member number, or other identifiers that should not be duplicated. If a user cannot save a record because of a duplicate value, search active and archived records before treating it as a bug.
Options
Use Options when users should choose from a controlled list, such as category, status, plan, region, or priority.Click Add option to add rows. You can also import options by CSV when the list is long.For option CSV import, prepare two columns: label on the left and value on the right. Headers are not required.
Conditional options
Use Conditional display when one option should limit another option. For example, selecting a parent category can limit the child categories that appear.Create the parent and child option properties, open conditional display settings, choose the child property, and define which child options should appear for each parent option.If conditional options do not appear as expected, check both option properties, the selected parent value, and whether the form includes both properties.
Grouped options
Use Grouped options when options should be shown under parent groups, such as domestic and imported origins.Add groups, then add option labels and values inside each group.
Tags
Use Tag when users need flexible labels that can be reused as suggestions later.Add the tag property to the form, then enter tags from the record screen.
Edit or delete properties
To edit a property, open Object Management, select the object, and click the property name.Update the settings in Manage property, then click Update.Properties that contain data cannot be deleted until the values are cleared from records.To delete a property safely, export or review the current values, clear the values from all active and archived records, confirm that reports, imports, workflows, integrations, and forms no longer depend on it, then delete the property.
Troubleshooting
A new property does not appear on the record form
Check whether the property was added to the form used by the current view. Creating a property does not always add it to every form automatically.
A property does not appear in the record list
Check the current view columns. Add the property to the view if users need to see it in the table.
A CSV import cannot map or save a property
Confirm the property name, type, required setting, unique setting, and option values. For option properties, imported values must match the configured values, not only the display labels.
A record cannot be saved after a property change
Check required fields, unique values, option values, and conditional option rules. Also check whether the form is missing a property that is now required.
A workflow, report, or integration changed after editing a property
Properties can be used by reports, dashboards, workflows, actions, integrations, imports, exports, and AI-assisted updates. Review those dependencies before deciding that the workflow or report is broken.
Checkpoints
Before changing a property in a live workspace, confirm the affected records and dependent configuration.
For form and view setup, see Views and Forms.
Use unique values for fields such as SKU, external ID, member number, or other identifiers that should not be duplicated. If a user cannot save a record because of a duplicate value, search active and archived records before treating it as a bug.
Click Add option to add rows. You can also import options by CSV when the list is long.
For option CSV import, prepare two columns: label on the left and value on the right. Headers are not required.
Create the parent and child option properties, open conditional display settings, choose the child property, and define which child options should appear for each parent option.
If conditional options do not appear as expected, check both option properties, the selected parent value, and whether the form includes both properties.
Add groups, then add option labels and values inside each group.
Add the tag property to the form, then enter tags from the record screen.
Update the settings in Manage property, then click Update.
Properties that contain data cannot be deleted until the values are cleared from records.
To delete a property safely, export or review the current values, clear the values from all active and archived records, confirm that reports, imports, workflows, integrations, and forms no longer depend on it, then delete the property.
