XEsSetProjectPropertyAction PropertyIdentName

EPLAN hat ja die Handhabung mit benutzerdefinierten Eigenschaften geändert.
Diese können nun über Optionen > Eigenschaften konfigurieren… geändert werden.

Leider hat EPLAN nicht gesagt wie man diese Eigenschaften dann auch Schreiben kann.
In der Action XEsSetProjectPropertyAction ist nur dokumentiert wie man die ID-bezogenen Eigenschaften setzt.

Es gibt, wie so oft, einen nicht dokumentierten Parameter namens PropertyIdentName mit dem man die Eigenschaften ansprechen kann.

Beispiel:

  • Projekt
  • Seite
  • Funktion
  • Artikelreferenz

Posted in EPLAN, EPLAN-Scripts and tagged , .

9 Comments

  1. Hi Jonny,

    I’m using 2.4 and cannot make this to work.

    I’ve tried:

    CommandLineInterpreter oCLI = new CommandLineInterpreter();
    ActionCallingContext acc = new ActionCallingContext();

    acc.AddParameter(“PropertyIdentName”, “EPLAN.Project.UserSupplementaryField51”);
    acc.AddParameter(“PropertyIndex”, “0”);
    acc.AddParameter(“PropertyValue”, “My project property”);
    oCLI.Execute(“XEsSetProjectPropertyAction”, acc);

    But no change on the Field (which I assume is the “Displayed Name” text box?).

    There are any need to change the other test boxes (Input aid/Category)?

    What do you think?

     

  2. I tested it, and for me it works…

    using Eplan.EplApi.ApplicationFramework;
    using Eplan.EplApi.Scripting;
    
    public class Test
    {
    	[Start]
    	public void Action()
    	{
    		CommandLineInterpreter oCLI = new CommandLineInterpreter();
    		ActionCallingContext acc = new ActionCallingContext();
    
    		acc.AddParameter("PropertyIdentName", "EPLAN.Project.UserSupplementaryField10");
    		acc.AddParameter("PropertyIndex", "0");
    		acc.AddParameter("PropertyValue", "My project property");
    		oCLI.Execute("XEsSetProjectPropertyAction", acc);
    	}
    }

     

  3. Hi Johann,

    I’m still in 2.4 HF2 and cannot move to 2.5 yet.

    Do you think this might be the reason?

    Have you tried this action in 2.4 (e.g. HF4)? Did it work then?

    Regards,

  4. Works also in 2.4 HF2.

    Are you sure that you change a project property?

    Try the script… i think your property is the wrong one.

  5. Hi Johann,

    Your script doesn’t work also :-C

    I’m already in 2.4 HF4 and cannot seem to be able to make it work. I’m using 32Bit not 64Bit. What about you?

    Also EPLAN Help is contradictory:

    XEsSetProjectPropertyAction 
    /PropertyId:? 
    /PropertyIndex:0 
    /PropertyValue:"?"

    They mention “PropertyId” instead of “PropertyIdentName” (as per your script) and that PropertyId = Idntifier of the property to be defined (= Property number)?
    The idea is to change the alias name, what you see in EPLAN dialogs, labels and filters e.g. instead seeing “EPLAN.Project.UserSupplementaryField nn” we could just see “MyPropName”.
    This is no different to what we had in 2.3.
    I don’t know what to do anymore…

     

  6. The action in EPLAN help is the old way, without the new (>2.4) naming of user definied properties.

    You can not change the name per script, only in the UI. With the script is it only possible to set values. For the names, go to Utilities > user properties (i have no english UI sorry).

  7. Hi Johann

    another question to XEsSetProjectPropertyAction:

    I want

    to copy from Project.USF10 to another Project.USF60
    delete Project.USF10

    is that possible? I tried to copy but I have no idea!

    Thanks for support!

    Gernot

    public class UPDATE_SCRIPT
    {
    
        [Start]
        public void USF_Update()
        {
            CommandLineInterpreter oCLI = new CommandLineInterpreter();
            ActionCallingContext acc = new ActionCallingContext();
            
            acc.AddParameter("PropertyIdentName", "EPLAN.Project.UserSupplementaryField60");
            acc.AddParameter("PropertyIndex", "0");
            acc.AddParameter("PropertyValue", "????");
            oCLI.Execute("XEsSetProjectPropertyAction", acc);
        }
    }
  8. Directly is it only possible by API.

    With Scripting you can export the property and read from file and set it to new one.

    Deleting is only possible by API.

  9. Thanks for Information! Maybe later I will come back for help!

     

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.