This looks like you are writing to the parameters which contain your tag paths, not writing to the tags themselves...? If these are considered to be input parameters - which contain the tag paths (as a string), I would never write back to them. After you click a button to write values to overwrite the tag paths, you are losing any reference back to the actual tags, which might be why your screen displays errors on each of those tags.
To keep things simple & straightforward, I would update your architecture to the following:
- Create a single input parameter on your view called Pompe_Path ( (view.params.Pompe_Path), which will be a string containing the tag path to your pump folder (or UDT). This will be the only parameter that you pass into this view, and you never write to it again.
- Create several view.custom parameters, which are indirect tag bindings to each of your tags. Where {1} below =
view.params.Pompe_Path
- view.custom.Var_Def : {1}/Var_Def
- view.custom.Var_Ma : {1}/Var_Ma
- view.custom.BP_Ma : {1}/BP_Ma
- etc...
- When building your graphics, reference the view.custom.xxxx parameters. Read / Write w/ bidirectional property binding to each of those properties everywhere in the view. Nothing within your graphics would need to reference the original input parameter (view.params.Pompe_Path).