Developer forum

Currently it requires an update to the template for the built in fields. Technically this comes from that the fields in the viewmodel are doubles and we cannot change them to be strings and include the units as part of the viewmodel.

We have a task going to implement a new property that holds the combined information on DW10.That will make the value available on the viewmodel, but will still require a template update in Swift as it will be a new property to support backwards compatibility.

BR Nicolai

Currently it requires an update to the template for the built in fields. Technically this comes from that the fields in the viewmodel are doubles and we cannot change them to be strings and include the units as part of the viewmodel.

We have a task going to implement a new property that holds the combined information on DW10.That will make the value available on the viewmodel, but will still require a template update in Swift as it will be a new property to support backwards compatibility.

BR Nicolai

Hi Nicolai,

Thanks for your fast response!

In that case, could you let me know how I can temporarily show the values including units, with updating the templates?

Also, could you clarify which templates would need to be updated, and how to apply those changes so the combined value becomes visible in the frontend?

Thanks again!