Message Definition Lines

In the subpage 'Lines' you can setup the tables and link these together, set filters. The following fields are available:

Field	Comments
Table No.	Choose the table as the data-source. The table indicates the fields you can use for the message definition.
Table Name	This is the name of the table. This is a flowfield and is automatically filled based on the field Table No.
Name	This becomes the Element Description in the XML file. For outbound processes this must be the same name as given in the WSDL. For example 'productData', 'websites', tier_price' is valid for the webservice catalogProductCreate For inbound webservices you have to enter the element name from the XML which you want to import, like import web orders. You can open the XML response and check which data is in the XML available. Enter the same description in the Message Definition as in the XML
Description	Enter your own comments to identify the purpose of a line, the system won't do anything with this information.
Filter Exists	Flowfield and indicates if the data is filtered.
Validate	Executes the OnInsert and OnModify trigger on a table. This trigger is not relevant for outbound processes, is only useful for inbound actions.
Response Field No.	When you run a 'Create' method in Magento for any entity, you will receive a result (id or number) from Magento. Choose the field in NAV where the response value must be stored. Leave blank if the result must not be stored.
Multi Line	Check this field if you use custom attributes from the type text-area. This means all text will be concenated in the XML.
Data Section	Check this field if you want to create a section in the XML. The section will get the name of the 'Name' field . Most needed when you are creating custom Message Definitions for custom Magento webservices which are not default
Custom Section	Check this field if you want to create a section in the XML for a standard webservice. The section will get the name of the 'Name' field .

Actions for the line

Part	Description
Card	Open the page with all additional settings
Links	Link two tables (parent and child) to each other, for example, Sales Header and Sales Line, define the fields on which the tables must be linked. In this case the link is established on the primary key fields: Document Type and No. For linking the Item table to any other table, you should always use the 'No.' field as a link. Linking 2 tables is required, otherwise you will run into problems
Fields	Page with all fields to generate in the outbound XML or to download from the inbound XML Message Definition Fields
Filters	Add filters to your tables, this will minimize the output
Copy Fields
Copy Links
Functions
Increase Indent	This function will link the 'child' section to the 'parent' section. Is always needed when you link 2 tables together.
Decrease Indent	This function will undo the link of the 'child' section with the 'parent' section.