Does this plant's IP range have a second byte that is less than 100 ?
1 Like
Here is a snap from the plant in question. The Plant ID is 191 which is the number assigned to the Site Number tag I am referencing.
No
This is from a screen inside the app itself and references the same session property.
Something isn't coming through as expected. Try showing us 3 side-by-side labels bound to these expressions in the plant where you are having the problem:
- left({this.props.address}, 6)
- '10.' + {[SITE_BOF]Site Number}
- label1.text = label2.text (referring to #1 & 2 labels above)
1 Like
I tried that also but like I said it works in the other plants with the same code but here is something I threw together in session.custom props. 'InPlant' is false because the Site Number on this gateway is 191 and my IP does not comply with the rules.
I doubt we'll be able to figure out why it doesn't work in that one location without seeing the results of those expressions in the location where you are seeing the issue.
1 Like
I was working with someone who was at the site and watching their screen through Teams. The results were as expected with nothing out of the ordinary except it was not making the item visible.
Does this mean InPlant was true as you expected, but the item wasn't visible? Or was InPlant false? Is it possible the inherited project isn't up-to-date at the one location that isn't working as expected?
No it did get it but didn't work. Since then I have been working directly with that designer code anyway.
Any chance your plant code tag has a space mixed in? In other words, not exactly three characters long?
I thought about that also but it was not adding a space which is usually my arch nemesis.
Please contact Support. We've exhausted our options and abilities here on the forum.
1 Like
10.191. is 7 instead of 6?
I saw a 92. in the example image you had posted, so I thought maybe the dot was mucking it up.
I figured out my problem. I new the project was inheriting from a global project and all the related session props were supposed to carry over during all pushes but what I didn't know was that if a manual change is made to the project that is inheriting, a folder is automatically created on the gateway which overrides inheritances no matter what you try to add. So in this case the custom session properties I need to be inherited, were being ignored. I had to erase the folders first to get the inheritances to work again. Here is the location of the folders I had to delete which were 'page-config' and 'session-props'. After they were gone everything worked. From what I understand this is the location on most any gateway to find them, minus the project name which would be different. Thanks for all the suggestions.
1 Like