Resource: dimensionitem.nv
HTTP-method: POST
Used for adding and editing cost objects in Netvisor. The cost object header of the cost object to be added must exist in the system.
Parameters used in the call:
| Parameter | Occurs | Description | Example |
| method | 1 | add or edit The XML message itself defines where in the hierarchy the cost object is added or which cost object is edited. | add |
| updateparentreference | 0...1 | Always true. Used only when editing a cost object, 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 you want to update an existing item, give the name of the item to be updated (*1 | Cost object |
| 2 | code | Text, Max. 50 | 0...1 | Identifier of the cost object (*3 | P001 |
| 2 | label | Text, Max. 200 | 0...1 | Name of the cost object (*3 | Website renewal |
| 2 | oldcode | Text | 0...1 | Old identifier, for identifying the cost object to be edited (*4 | P001 |
| 2 | oldlabel | Text | 0...1 | Old name, for identifying the cost object to be edited (*4 | Old project |
| 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 | fathercode | Text | 0...1 | Identifier of the higher-level cost object (hierarchy) (*5 | P000 |
| 2 | fatherlabel | Text | 0...1 | Name of the higher-level cost object (hierarchy) (*5 | All projects |
| 2 | activityperiodstart | Date | 0...1 | Start date of the validity period | 2026-01-01 |
| 2 | activityperiodend | Date | 0...1 | End date of the validity period | 2026-12-31 |
| 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
Notes on the renewed cost object handling:
*3) When code / label is given, they override the item element
*4) When oldcode / oldlabel is given, they override the olditem element
*5) When fathercode / fatherlabel is given, they override the fatherid element
Did you find it helpful? Yes No
Send feedback