🚨New Feature Update🚨 - Discrete Values is Now in Production

[jessica_smith]

Release Notes

We are happy to announce the support of Discrete Values in Autodesk Tandem. Now, our users can visualize string data in their digital twins, expanding the data support offerings for sensors.

• Users can define a parameter with text and apply the strings as restricted values.
• Users can visualize the string data in the Connections cards.
• Users can visualize the data in the Charts and combined charts.

[Chad-Smith]

Thank you very much team for this.

It now opens up a whole data trove that I have been waiting to explore and implement. In fact, I've been holding off on the purchase of some sensor that produce this data until it was available in Tandem.

[Chad-Smith]

In charts with discrete values, can the colours be permanently customisable?

The use case being that certain values might be viewed negatively, and so you might want to use an appropriate colour like red. While other values might be viewed positively and want to use other colours like green, blue.

[Chad-Smith]

A couple more questions.

1. It would appear that the discrete values are Case Sensitive. Was this deliberate to address a certain use case? My preference would be for them to not be case sensitive.
2. I know these are called Discrete values and it appears that they must be defined. But will there be an option to not define them in the Tandem Parameter?
   Examples:
   1. I want all values from a sensor (which can be many) to be visible in Tandem. When needing to define them manually in the Parameter, it's easy to miss one.
   2. I might have a generic Parmeter called 'Status' which could be applicable to a large variety of sensors and devices, with each of these having their own unique set of values. This now greatly expands the total values which that Parameter might have.

I can appreciate that some Discrete Parameters might need very specific values defined, almost like a filter. But in other cases, I want all values.

When I tried not defining the values I kept getting errors. So if the above is possible, some guidance would be very welcomed.

Thanks.

[tstanev]

You can pick a color when defining the list of accepted values.

[tstanev]

The list of acceptable values must be defined up front because we map the textual representation to something more compact for storage. All unknown values will appear in the same way (they won't be visualized in a distinct color, etc).

The use case you mention is well understood and reasonable, but not currently supported by our implementation -- it will require further work in our backend to support which we have not yet planned.

[Chad-Smith]

@tstanev Thank you for the follow up posts.

Looks like my question about colour and your reply is timely, with the feature only just been released.