Asset Custom Fields

While creating an asset, Strobes provides several default fields. The default fields change based on the type of asset being added. Apart from the default fields, if the user needs to add his own fields, he can achieve that using custom fields. In order to use custom fields, a user will have to define the custom fields first.

Types of Custom Fields

There are nine types of custom fields which can be defined. They are as follows:

  • Text: This field expects text. There is no limit to the number of words that can be input in this field.
  • Number: This field expects a number. Only one number can be entered per Number custom field.
  • Date: This will be a date picker from which you can select a date. Only one date can be selected per Date custom field.
  • Boolean: This field expects a boolean value. The value can either be 'Yes' or 'No'.
  • Select: You can define any number of options for this field, out of which it is expected that only one option will be selected.
  • MultiSelect: You can define any number of options for this field, out of which you can select one or more options.
  • Email: This field expects input in an email address format.
  • User: This field will be a dropdown of all the users which have already been added to your Strobes organization. You can select one or more users.
  • URL: This field expects a URL as an input. Only one URL can be entered and if an appropriate URL has not been added, then the entered data will not be saved.

Defining Custom Fields

The following are the instructions to define custom fields:

  • Navigate to 'Settings' and click on 'Custom Fields'.

  • Select the 'Assets' tab.
  • Click on 'Add new field'.
  • Select the type of field you need to add.

  • Provide a 'Field name' and 'Description' for that field. Also select if that field is a 'Mandatory Field' or not.

  • Click on 'Save' and the custom field will now be available while creating or editing assets.

Using Custom Fields while Creating Assets

Once you have defined the custom fields, the next time you create assets, you will find the option to add data into the custom fields which you have defined.

  • Navigate to 'Assets'.
  • Click on 'New Asset'.
  • Along with the default asset fields, the custom fields which you have defined will also be available.



Using Custom Fields while Editing Assets

Once you have defined the custom fields, the next time you edit assets, you will find the option to add data into the custom fields which you have defined.

  • Select any of the created assets.
  • Click on 'Edit'.
  • Along with the default asset fields, the custom fields which you have defined will also be available.



Using Custom Fields with Asset CSV Import

For every custom field that you define, a 'Slug' will be generated corresponding to it as shown below.


You will have to use that slug as a header in the CSV file which follows the Strobes format as 'custom_slug'. The following are how the values can be passed in the CSV file:

  • Text: There is no expected format for this. You can pass any text you need.
  • Number: The expectation here is that only numbers will be passed like '0123456789'. If any other characters are included here, then the import will not be successful.
  • Date: The expected format is "%Y-%m-%d". Example "2023-05-30".
  • Boolean: The expected value here is either 'True' or 'False'.
  • Select: The expected value here is one of the options which you have added while defining this custom field.
  • MultiSelect: The expected values here are one or more of the options seperated by a comma from the options which you have added while defining this custom field.
  • Email: The expected value here is a valid email address. Only one value can be passed here.
  • User: The expected values here are one or more ids of the users added onto Strobes seperated by a comma.
  • URL: The expected value here is a valid URL. Only one value can be passed here.

You can find a sample CSV file here.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.

Articles in this section

See more