I have created a project where our coordinators enter in information based off their shift and department. We have 3 different shifts and 15 different departments so each coordinator selects their shift and department and then enters their numbers for the day. But what we are finding is that if more than one coordinator is using the Entry page I have created for the numbers to be entered, when they select the submit button, the information that is going into our SQL database appears to get “mixed up”. Or if one of the coordinators is in the screen, and another one somewhere else on another workstation is selecting buttons, then the first coordinator can “see” those buttons changing color on his workstation as if he were the one selecting them. I thought that if the same project was being used by multiple people(on different workstations) then this should not be an issue. Is there a way to resolve this?
Bind to client tags instead of gateway tags. Gateway tags are global everyone, so everyone sees the same thing. Client tags are local to the user.
So are you saying put the tags in the client folder of the tag browser instead of being under the default tag folder?
Exactly right.
so can I just “move” my existing tags or do I have to actually recreate all new tags?
Nevermind… just got my answer…LOL. cannot move them. Not compatible.
hi can you explain more on how to do this?
There's a tag provider for Vision called, in v8, Vision Client Tags. These are client-specific tags independent to each client launched, rather than being shared like standard tag providers are. Meaning, these tags will have independent values for each client launched. This doesn't apply for Perspective where you should use custom Session props instead
Hi Sir,
I am actually using perpective for this project, is there a equivalent tag for perpective?
Do you have insigths on Perpective custom session props?
There's actually not much in the UM for custom session props, but you can just create your own and attach bindings to them and/or read/write to them from your Views. They act the same as Vision Client Tags in that each session has an independent set of session props.
Thank you!,
Ill explore the session props