Hi,
Have been attempting to utilise nHaystack on a Niagara station which is loaded with the 'Niagara4' haystack dictionary, this uses the fixed namespace of:
h4
My understanding of the Prioritized Namespaces value is that nHaystack queries should be able to resolve components/tags from dictionaries using a namespace other than 'hs'. I have attempted to add tags to Niagara components (site/equip/points etc) both ad-hoc and implied from different dictionaries (name spaces) and the nHaystack service does not seem to resolve these despite add the namespace to the Prioritized Namespaces slot.
Hoping this can be resolved as it seems Niagara have put some work into the h4 dictionary with regards the implication of supertype tags which I would like to leverage.
Hi,
Have been attempting to utilise nHaystack on a Niagara station which is loaded with the 'Niagara4' haystack dictionary, this uses the fixed namespace of:
h4
My understanding of the Prioritized Namespaces value is that nHaystack queries should be able to resolve components/tags from dictionaries using a namespace other than 'hs'. I have attempted to add tags to Niagara components (site/equip/points etc) both ad-hoc and implied from different dictionaries (name spaces) and the nHaystack service does not seem to resolve these despite add the namespace to the Prioritized Namespaces slot.
Hoping this can be resolved as it seems Niagara have put some work into the h4 dictionary with regards the implication of supertype tags which I would like to leverage.