Resource: dimensionitem.nv
HTTP-method: POST
Used for adding and editing cost objects in Netvisor. The cost object header to be added must exist in the system.
Parameters used in the call:
| Parameter | Occurs | Description | Example |
| method | 1 | add or edit XML determines where the cost object is added in the hierarchy or which cost object to edit. | add |
| updateparentreference | 0...1 | Always true. Used only when editing cost objects, enables changing the cost object hierarchy. | true |
The data to be imported is sent with the call as XML according to the following description (POST-data):
| Level | Element | Type and length | Occurs | Description | Example |
| Root | root | Aggregate | 1 | ||
| 1 | dimensionitem | Aggregate | 1 | ||
| 2 | name | Text Max. 50 |
1 | Name of the cost object header under which the cost object is created | Cost object header |
| 2 | item | Text Max. 200 |
1 | Name of the cost object. The cost object header must be established in Netvisor before adding the cost object. | Cost object |
| 2 | olditem | Text | 0...1 | If updating an existing one, give the name of the item to be updated (*1 | Cost object |
| 2 | fatherid | Numeric | 0...1 | Id of the cost object in Netvisor under which the new object is created in the hierarchy (*2 | 0 |
| 2 | fatheritem | Text | 0...1 | Name of the cost object in Netvisor under which the new object is created in the hierarchy (*2 | New cost object |
| 2 | ishidden | Boolean | 0...1 | Is the cost object hidden: True or False True=hidden, False=visible |
true |
Notes on the content of the XML message when adding and editing cost objects:
*1) Element olditem is mandatory when editing an existing cost object, regardless of where the object to be edited is in the hierarchy
*2) Elements fatherid and fatheritem are mandatory when a new cost object is to be added under an existing cost object, i.e., at a lower level in the hierarchy
Did you find it helpful? Yes No
Send feedback