The following list describes the assumptions and limitations of Microsoft Dynamics NAV Connector:
•The user must be a domain user and must be the Windows Login list to access the Navision Web Service.
•The user can perform read and write operations by using card type pages. The list type pages supports only read operations.
•When you read data from NAV, the size of the data that can be handled depends on the string variable limit.
•When you update the records, you must remove the system fields such as Last_date_modified from field mapping.
Microsoft Dynamics NAV Connector supports the following basic filters:
•INSERT
The field name key must be present at the parent level. If a child key is present, the field name KEY_1 must be present at the child level. You do not need values for the key field to run an insert operation. If the key field has a value, the insert operation ignores key field values and inserts a new record in the database.
A parent entity can have multiple child entities. A parent record can have multiple child records.
When you insert a child record into a parent record, the parent record must have an appropriate value for the key field. The child record must have null value for the key field. If the fields are auto populated when you insert entities, you must remove the auto populated fields.
For example, if you provide the value for the field Sell_to_Customer_No in SalesInvoicePage, then the value for the fields Sell_to_Customer_Name, Sell_to_Customer_Contact_No, Sell_to_Address, Sell_to_Post_Code generates automatically using Sell_to_Customer_No value. Hence, remove the fields Sell_to_Customer_Name, Sell_to_Customer_Contact_No, Sell_to_Address, Sell_to_Post_Code when you insert data into SalesInvoicePage.
•UPDATE
When you invoke an update operation, the values for key field must be present for both parent and child record.
•UPSERT
If the record does not have a value for the key field, the record is inserted in to the database. If the record has a value for the key field, the record is updated. If the value of the key field does not match, an error message appears.
•DELETE
You must provide both parent key and child key to delete a record.