Discuss and solve problems in energy management and automation. Join conversations and share insights on products and solutions. Co-innovate and collaborate with a global network of peers.Register Now
>>Message imported from previous forum - Category:Bulk Edit Tool<<
User: ROVSCADAENGINEER, originally posted: 2019-06-12 02:24:38 Id:447
I have been having some discussion with my senior engineer about using the bulk edit tool to roll out and eliminate manually updating several state name configurations on the server. We both have concerns about using the bulk edit tool on the live server when changing simple point configurations like state descriptions on points etc. These should not impact the overall operation of the system but We are concerned about what the risks would be of implementing such a tool for making these changes on a live system. If possible would you be able to shed on light or recommendations on the matter? What is your past experience with using this tool on the system? I have read in the bulk edit tool user guide that sometimes unexpected system changes could take effect. I am assuming here that this Is to do with overlooking the effect before implementing changes on a system. Or is this an indicator clearly in software glitches within the program itself? Would be good to hear about your experience with using this tool.
Reply User: tfranklin, posted: 2019-06-12 12:59:57
Measure twice, cut once! If you're having second thoughts about importing something on a live server then you probably shouldn't be importing it on a live server. That said, I do it fairly often. As long as you're confident in the content that you're importing and double check that you're only going to be updating the fields that you expect to get updated then you should be fine.
I'd also encourage you to err on the side of caution if you're updating templates and instances with the same import. After you run an import you may find your instances locked down from changes because the templates are still propagating the changes down to the instances.
Basically, I think you'll more than likely be fine if you're smart with what you import and don't import more than what you need.
Reply User: geoffpatton, posted: 2019-06-12 15:29:56
I think that errors line is to be clear that you need to be sure you know the effect of everything you are changing and that Schneider is not responsible.
I have made changes that I ultimately did not want to with Bulk Edit. I can't remember anything specific, and most have been while editing a development system.
If I am just editing one field in a few objects with the quick edit I don't worry about it but for larger edits I am more cautious.
If I am using the quick edit on a lot of objects I will make an sde Export of the database or the section being edited first. Then I can always import that back in to revert back to where I started.
Before editing a Bulk Edit export I save a copy, so I can undo changes by importing it back in.
Reply User: ROVSCADAENGINEER, posted: 2019-06-12 21:25:06
thanks for the intel guys.