2 of 2 people found this helpful
This behavior was discovered as an issue in PI Vision 2017, but has been resolved in PI Vision 2017 R2. What version of PI Vision are you using?
You are correct that this behavior is caused by the ampersand (&) in the attribute path. The ampersand is a control character in URL formats and need to be encoded properly if they are used not as a control character.
Yes, we are using PI Vision 2017 right now. Is there any workaround for this until we upgrade to PI Vision 2017 R2.