Option --fields not working on some items

@"Horia.Culea_1P" Thank you for the reply.
The fields listed in the json format are the following:

```json
"fields": [
{
"id": "",
"type": "STRING",
"label": "password",
"value": "**"
},
{
"id": "",
"type": "STRING",
"label": "username"
},
{
"id": "",
"type": "STRING",
"label": "fname",
"value": ""
},
{
"id": "",
"type": "STRING",
"label": "lname",
"value": ""
},
{
"id": "",
"type": "STRING",
"label": "company",
"value": ""
},
{
"id": "username",
"type": "STRING",
"purpose": "USERNAME",
"label": "email",
"value": "*"
},
{
"id": "password",
"type": "CONCEALED",
"purpose": "PASSWORD",
"label": "password",
"value": "*",
"entropy": 379.5647,
"password_details": {
.... etc
}
},
{
"id": "",
"type": "STRING",
"label": "rpassword",
"value": "*"
},
{
"id": "",
"type": "STRING",
"label": "source",
"value": "****"
},
{
"id": "",
"type": "STRING",
"label": "agree",
"value": "✓"
},
{
"id": "",
"type": "STRING",
"value": "Create New Account"
},
{
"id": "notesPlain",
"type": "STRING",
"purpose": "NOTES",
"label": "notesPlain"
}
],

```

If I open the item from the Linux client I can only see "username", "password", "página web" (spanish website) and "website", exactly the ones that have an ID in the json list.
The op read op://vault-name/item-name/field-name works as expected.

Taking a different item as an example I can see that there are fields that could even miss the label property:
json
{
"id": "",
"type": "STRING"
},


Hope this information is enough to help figuring out the problem.