Accessing parameter units in reports?

[miggland]

I'm testing out reports - or labels to be more specific.

I can successfully use the following to get an output:

<p>Params:<br />
{% for k,v in parameters.items %}
 {{ k }}: {{ v }} <br />
{% endfor %}
</p>
<p>
{{ parameters }}
</p>

which looks like this:

What I'm missing is the parameters unit, in this case 'mm' - any way to easily access this?

[SchrodingersGat]

I think something like the following should work:

{% for param in part.parameters %}
{{ param.template.name }} : {{ param.data }} {{ param.template.units }}
{% endfor %}

Note here that you're using part.parameters to directly access the parameters, not the top-level parameters object which returns the simplified dict object.

[matmair]

@SchrodingersGat that might need to be included in the docs.

[miggland]

I can't get that to work, I get an error:

{
    "error": "TypeError",
    "error_class": "<class 'TypeError'>",
    "detail": "'RelatedManager' object is not iterable",
    "path": "/api/label/part/2/print/",
    "status_code": 500
}

This appears for parts and for stock items, whether the part has parameters or not.. Adding {% if part.parameters %} around doesn't help either.

[SchrodingersGat]

Ah, try {% for param in part.parameters.all %} ?

[miggland]

OK, that works:

{% for param in part.parameters.all %}
  {{ param.template.name }} : {{ param.data }} {{ param.template.units }}<br />
{% endfor %}

Definitely something which should be in the docs :)

Wouldn't it make sense to include the unit in the string output which is in parameters? I would assume including the unit would be the more common use case, and any calculation or so requiring the raw data less common - that case would then use the syntax above?