F

Fieldra

In the studio

Using Fieldra

Fieldra works in the Shopify admin. It is not on the App Store. These are the jobs merchants use it for: a bulk edit, a preview, an automation's result, and an editor that matches the custom field.

Bulk-edit products or customers

1. Open the bulk editor and create a bulk edit.
2. Choose Products or Customers. Variants and collections are the other choices. Orders are not a choice here.
3. Search for the custom field and select it. If the list is empty, go back and bring the fields in from Shopify first.
4. Choose Update value or Delete value. The value box changes to match the field. See Editors that match the field.
5. Narrow the set if you need to. Products, collections, and customers accept the same search you use in Shopify admin, such as tag:sale, vendor:Nike, or status:active. Leave it blank to include every record of that type. Variants cannot be filtered: a variant edit covers every variant.
6. Read the preview, then save. The edit is created as waiting. Run it from the list when you are ready.
7. Open the run to see each record's result. If the whole run failed, use Retry. While it is still waiting or running, you can cancel it. While it is still waiting, you can open it and change it.

Preview before you run it

The preview sits beside the form and fills in once the record type, the custom field, and the action are set.

• How many. The count is the number of products, variants, collections, or customers that match, not a guess.
• A sample. Each row shows the record, the value it holds now, and the value your edit would write. A delete shows that the value would be cleared. The sample can be shorter than the full count.
• Nothing matched. If no record fits, the preview says so. For a delete, that usually means the field is not set on those records. Widen or clear the filter and look again.
• Open the record. A row can link to that product, variant, collection, or customer in the Shopify admin so you can compare the current value.

Do not run a catalog-wide edit until the count and the sample look right.

See whether an automation ran

1. Create an automation and name it.
2. Choose how often it repeats. Presets include every hour, every day, a weekday, and the first of the month. You can also set your own daily, weekly, or monthly time. Times are in UTC.
3. Choose products, variants, collections, or customers, then the custom field. Set the value, update it, or clear it. The same filter rules as a bulk edit apply, including the variant limit.
4. Save it. On the automations list, each rule shows one status: Scheduled, Pending, In progress, Completed, Failed, or Paused.
5. A completed run is done. A failed run is the one to inspect. Pause stops a rule you do not want to repeat. You can resume it later.
6. Run now is available when a run is not already under way. The status moves to pending, then in progress, then completed or failed.

Search the list by name, or filter it by status, when you only need to know whether last night's rule finished.

Editors that match the field

The value control follows the kind of custom field. You should not have to invent the format.

Kind of field	What you fill in
Yes / no	True or false
Whole number or decimal	A number
Date	A date
Date and time	A date and a time
Link	A web address, or link text plus the address
Color	A color value
Money	An amount and a currency
Measurement	A number and a unit
Rating	A rating on a scale
List	One item per line
Longer text	Lines of text

If the field is a kind Fieldra does not have a special control for, you get a plain text box. When the value is rejected, switch to the control that matches the field instead of retyping the same text.

When a result looks wrong, use troubleshooting before you ask for the app to be removed and added again. Removing it does not fix a custom field that was never turned on.