Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

The add-property command. Expanding the schema of a type with custom properties

The add-property command. Expanding the schema of a type with custom properties

The add-property command supports creating custom properties on an existing type. 

The syntax of the command is 

add-property -type <typeName> -xmlFile <pathToPropertyDefinitionXmlFile> | -xml <property definition xml string> -s "user[:password]@host:port" [ -epwdfile "pathToPasswordFile" ]

Note that either -xmlFile or -xml must be specified, but not both.

The xml is different for each property type, and must obey the custom component syntax  (schema examples below). Note that after the command completes, the server automatically prepends Usr_ to the property name.

Creating properties through the command line provides an alternative to creating them through the Cross Platform Client. Ideally, the server will be in exclusive administration mode when creating properties, so that all other users will not be affected. Property creation is slow and expensive, since the database schema and metadata change, the database view member table has to be filled with the appropriate defaults, etc.

examples of property definiton XML for various property meta-types

  <Property name="anInteger">

    <DisplayName default="bar"></DisplayName>





    <Property name="aLongInteger">

    <DisplayName default="aLongInteger"></DisplayName>





    <Property name="aDouble">

    <DisplayName default="aDouble"></DisplayName>





    <Property name="aDatenTime">

    <DisplayName default="aDatenTime"></DisplayName>





    <Property name="aDateIgnorTime">

    <DisplayName default="aDateIgnorTime"></DisplayName>





    <Property name="aTimenSpan">

    <DisplayName default="aTimenSpan"></DisplayName>






    <Property name="aBoolean">

    <DisplayName default="aBoolean"></DisplayName>





    <Property name="aStringnThing">

    <DisplayName default="aStringnThing"></DisplayName>



    <DefaultValue>a stitch in time</DefaultValue>



    <Property name="anArrayOIDs">

    <DisplayName default="anArrayOIDs"></DisplayName>






    <Property name="aPrincipalID">

    <DisplayName default="aPrincipalID"></DisplayName>





    <Property name="aBucketOBits">

    <DisplayName default="aBucketOBits"></DisplayName>




    <Property name="aSetOPieces">

    <DisplayName default="aSetOPieces"></DisplayName>




    <Flags multiselect="true"  supportsProcessRules="false"/>

      <Enum code="100">

      <EnumName default="Windows"></EnumName>



      <Flags selectable="true" isClosedState="false"/>


      <Enum code="101">

      <EnumName default="Linux"></EnumName>



      <Flags selectable="true" isClosedState="false"/>





Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2016-09-26 17:56
Updated by:
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.