CSV to Prop script. Edit multiple objects and properties using Excel.

[APA]

Hey all,

With the attached script you can set object properties using a CSV file.

 CSV File needs to be CSV UTF-8 where ";" is used as a separator and "," as a decimal separator

You can create a template file with in run mode Prop to CSV mode.

And specify the objects you want to configure copying them from workstation search Window to the parameter. And specify the output file. Then you can edit the file in excel or text editor.

Example file looks like this:

And edited file could look like this:

If you want to make bindings use {bind} tag in the front of the value.

So it functions similarly to Workstations import from XLSX functionality, but the objects can be in different locations.

Examples this script can do, where there is not a straight way to do in Workstation:

• Set colors or line presentation of Log series in Trend Charts
• Set BACnet alarm properties (delay and limits - these are not exposed to normal search)

[JohnnyCarlsen]

Powerfull tool, I have been using at lot 💪

[Siva.A]

is there any way to extract the graphics used components properties in csv format??

[APA · Accepted solution]

TGML Component properties are visible trough SDK. Only when they are set to public exposes they can be seen as properties of the TGML. To get the component properties that are not public exposes, someone would need to make a script to analyze the TGML:s structure directly.

Short answer. It is possible. But someone needs to develop such a script for that purpose.

[Siva.A]

Thanks for your valuable answer. Is there any plan to develop such a code??. We are doing many custom graphics in our team and we are struggling to validate the graphics. if we get that scripts it will help us to compare the software & graphics and find out the issues..

[StefanLundin]

Hi Siva,

I'm happy to see you recognize the value of what Seal Script can accomplish. I'm now writing as part of the developing team for the Seal Script engine itself, even though your previous conversation has been with individually very competent people who are not part of our team but have excellent knowledge of creating Seal scripts and are doing so for their businesses.

As for our developing team, we do not typically develop specific scripts. We as a team mainly focus on developing the Script engine itself to ensure it has the features needed for script development, even though we do create more common scripts occasionally. Community members, in general terms, tend to develop scripts that benefit their own organization's tasks.

You can certainly use the community to ask if anyone has plans to develop a script that you could benefit from or if someone with the necessary skills could create a specific script for you. However, realistically, waiting for someone to have spare time to develop a specific script might take a while.

The best way to get a script that benefits your organization is to ensure that someone in your team learns to code Seal scripts. The knowledge required to gain this competence includes learning to code in JavaScript and understanding how Ebo objects are built up. The community will be a great resource and conversation partner when you encounter challenges.

With this, I want everyone, not just you, to consider developing such competence within their business. I'm sure it would pay back quickly.

Best of luck with your projects

[APA]

No sorry. I don't have plans to develop this kind of script.