Available from versions: Plugin Builder - 1.60.16.2 or higher
View information about the attributes of the Integration XML with the ERP Insight Plugin, by clicking directly on one of them:
NOTES: The TOPSURFACE_GRAIN, BOTTOMSURFACE_GRAIN and BOM_TYPE attributes can be added to the integration XML with the Insight integration plugin.
TOPSURFACE_GRAIN
The TOPSURFACE_GRAIN attribute defines whether the top face of the item has material with a vein direction.
Type: boolean, TRUE or FALSE.
The value of this attribute will be sought in the registration of the material applied on the upper face of the item.
If the material applied to the top face of the item has a vein direction the value will be TRUE, if it does not have a vein direction the value will be FALSE.
Examples:
- Attribute TopSurface_Grain with value FALSE:
- Attribute TopSurface_Grain with the value TRUE:
BOTTOMSURFACE_GRAIN
The BOTTOMSURFACE_GRAIN attribute defines whether the bottom face of the item has material with a vein direction.
Type: Boolean, TRUE, or FALSE.
The value of this attribute will be sought in the registration of the material applied on the bottom face of the item.
If the material applied to the bottom face of the item has a veindirection, the value will be TRUE, if it does not have a vein direction, the value will be FALSE.
Examples:
- Attribute BOTTOMSURFACE_GRAIN with value FALSE:
- Attribute BOTTOMSURFACE_GRAIN with value TRUE:
BOM_TYPE
The BOM_TYPE attribute tells you the type of material.
Type: text
This attribute will be displayed in the structure items, if it has a registered value.
Example of BOM_TYPE attribute presentation:
Configuration of the BOM_TYPE attribute
To register the Bom_Type attribute that will be inserted in the XML the configuration:
1. Access Registry - Budget - Structures.
2. In Structures - Structure, select the structure that needs to add the information. Access the Builder tab, and enter the desired value in BOM_TYPE.
IMPORTANT: By default, the BOM_TYPE field will be empty.
PHANTOM
The PHANTOM attribute shows the information where the items are phantoms, so they will not be presented in XML.
Code example to be inserted:
HASHSTRUCTURE
The HASHSTRUCTURE attribute will be displayed on all items that have children.
Code example to be inserted:
LINE_TYPE
The LINE_TYPE attribute is used to identify a grouping item, in order to organize the order and/or budget. By definition, this grouping attribute must not be below a product level.
EXAMPLE:
Below, an example of XML with LINE_TYPE attribute applied to the item:
Tags available from Builder version 1.60.20.4:
IDCATEGORY
The IDCATEGORY attribute is used to identify the identifier of the category to which the item belongs.
Below is an example of XML with the IDCATEGORY attribute applied to the item:
UNIT
The UNIT attribute is used to identify the type of unit of measure the item's quantity is in. Below is an example of XML with the UNIT attribute applied to the item:
REDEFINITION
The REDEFINITION attribute is used to identify in items with margin redefinition the margin redefined in the library.
Below is an example of XML with the REDEFINITION attribute applied to the item:
REPETITION
The REPETITION attribute is used to identify the repetition of a particular item in the environment. For libraries with Builder, this value is always 1.
Below is an example of XML with the REPETITION attribute applied to the item:
IDPRICEPROVIDER
The IDPRICEPROVIDER attribute is used to identify the identifier of the price provider. It normally has no value when there is only one provider, in this case Price.
Below is an example of XML with the IDPRICEPROVIDER attribute applied to the item:
PRICE
The PRICE attribute is used to search for prices online using the reference contained in the attribute (it is usually presented by the COMPLETE reference).
Below is an example of XML with the PRICE attribute applied to the item:
QUANTITY
Enter the quantity of the item.
FILECREATION
Enter the date and time the file was generated.
ASSISTANCEORDER
Tell us if it is a Technical Assistance project.