Looking for a better way to manage Persistent Variables.
We tend to have local vars in our FBs that need persistence through downloads as the systems are updated/altered on a regular basis.
Retain would suffice if we had an easy mechanism to backup and restore like we can with Persistent variables and recipes. Although not having to remember that step with Persistent variables is preferred.
We're running into issues with persistent storage capacity (WAGO PFC200) using the Persistent variable list (and adding all instances).
It appears there are many ways to handle this, some with recipes, some with files, others with application manager. Is there a solution that exists that is as simple as declaring as Persistent and managing elsewhere? Or do we need to move onto periodically writing CSVs?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Looking for a better way to manage Persistent Variables.
We tend to have local vars in our FBs that need persistence through downloads as the systems are updated/altered on a regular basis.
Retain would suffice if we had an easy mechanism to backup and restore like we can with Persistent variables and recipes. Although not having to remember that step with Persistent variables is preferred.
We're running into issues with persistent storage capacity (WAGO PFC200) using the Persistent variable list (and adding all instances).
It appears there are many ways to handle this, some with recipes, some with files, others with application manager. Is there a solution that exists that is as simple as declaring as Persistent and managing elsewhere? Or do we need to move onto periodically writing CSVs?