GeoSCADA - Visual Basic Error when trying to update the name of an instance through the CSimportV7 Excel Tool

[Anonymous user]

Hi all,

I'm trying to update with the CSimportV7 tool the name of some instances, but it pops up the following error message:

I've tried updating other parameters in the same instance, and it worked well. I think it may not be possible to edit the "Name" parameter. Any help? Thanks!

[BevanWeiss]

I'm not familiar with this tool.  Was it sourced from Schneider directly?

If it's not a Schneider product, then you probably need to look more to the original author to get detailed support on what the error messages them selves mean.

If this is indeed a Template Instance, then you are not able to rename items that inherit from the Template.  This is just a 'thing', it is the way, and there is no change anticipated for this (and I'd be very strongly against any such proposed change, since it doesn't make sense in regards to Template inheritance).

If you want the Template Instances (all of) to have a different name for this object, then you should rename it in the Template itself.

If you want just a few Template Instances to have a different name for this object, then it sounds like what you really want is for them to inherit from a different Template entirely.

[AndrewScott]

HRESULT error code C0040006 = OPC_E_BADRIGHTS = "The item's access rights do not allow the operation."

[Anonymous user]

Hi! Yes, this tool is provided by Schneider Electric. You can find it in the Resource Center (https://community.se.com/t5/Geo-SCADA-Knowledge-Base/Resource-Center-Home/ba-p/279133)

Regarding the renaming, what I want to rename is the Instance's name, which I've previously done manually. I know that the Instance's items cannot be renamed, unless by renaming the Template's items. But I've never had any issue renaming the whole Instance's name (manually).

Thanks!

[BevanWeiss]

I think you're right that in this situation changing the name may not be possible in this way.

There is a .Rename() method in the Client API, and my memory tells me that I had to use this (or the equivalent in the Automation Interface) to rename objects rather than just writing to their 'Name' property (which is marked as Read-Only in the schema).

If there are only a few to update, you could do it by hand.

If there is an easy rule for the renaming of many items, then you could likely do it using the SQL engine, it has some slightly different rules and I really do remember just being able to update the name field using SQL.  Just be careful that you get the WHERE query correct... with great power comes great opportunity to mess up.

Or you could dive into some VBA and write the Automation Interface based code to do the rename in Excel.