gender
Optional Field
This field is optional, but omitting it may leave out functionality on Prisjakt for your offers
Description
Specify the gender your product is designed for.
Effects When Used
- Customers can accurately filter products they want
Related Fields
Allowed Enum Values
female
male
unisex
Validation Rules
- Value must be one of the allowed enum values
Best Practices
Do
- Use standard values
Don´t
- Don't add info like
none,NA
Example Values
Here are examples of how a valid gender value should look like in XML and CSV (with header) respectively.
- XML
- CSV
Valid Value
<g:gender>female</g:gender>
Click to show more valid XML examples
<g:gender>female</g:gender>
<g:gender>male</g:gender>
<g:gender>unisex</g:gender>
Valid Value
gender
female
Click to show more valid CSV examples
gender
female
gender
male
gender
unisex
Error Codes
Below you will find possible error codes generated when validating this field alongside with an example in XML and CSV that would trigger the code. Please refer to the validation rules to understand the cause.
- XML
- CSV
<g:gender>unknown</g:gender>
danger
Properties
| Property | Value | Description |
|---|---|---|
| Data Type | enum | Closest data type in code |
| Nested | False | Defines if this field consists of one or more sub-fields |
| Case Sensitive | False | If small or large letters matter for this field |
| Repeatable | False | If you can supply multiple items of this field (it´s a list) |
| Repeatable limit | 0 | If a list, this specifices the max number of items |
Changelog
📅 2022-12-07
Added
Initial definition