Indirect bindings resolve order in regards to templates and historian

Ignition
1

Vision 8.1.38

More of a nuisance, but if there's a simple solution, I'd like to know, or if I'm doing something wrong:

I have a template with a sparkline that resolves to an indirect partial path passed to the template custom property. I do have a default value typed into this custom property. Within the template, this property is an indirect within the sparkline to the historical tag path.

On client startup, and likely when this window with the templates is opened, i get a database entry error in the gateway logs, and the path part that uses the custom property is Null. So somehow the sparkline is querying the historian with an unformed path. Then, of course after that, no more errors, as presumably the property resolves to the binding and all is well.

Its not causing any issues other than irrelevant entries in the logger. But is there a better way to avoid this?

2

I think a lot of people have used fadeIn animations to hide the errors while loading.

You could check the Overlay Opt-Out too, but if the binding does legitimately error out, you won't see the overlay. Also, check out the Publish Initial Uncertain Value.
Tag Bindings in Perspective | Ignition User Manual

3

Thanks, but Vision, not perspective.

4

Ah, my bad. Maybe you could use another custom property to hold some initial data, then use a coalesce() expression on the data property to default to your initial data while the tag history populates.

coalesce(
	{Root Container.Sparkline Chart.tagHistory},
	{Root Container.Sparkline Chart.default}
)