Sometimes an eform EForm is used to write to an AX AppXtender application. When designing the eformEForm, there are 2 situations you must be aware of any in AppXtender.
All required fields in the AX
...
Application must be filled in on the EForm for the data to be accepted into AX. If the required fields do not have a mapping established and data is submitted to AX, the entries will be rejected.
If the data type for an AX field is a user defined list, the entry on the EForm must match one of the values in the AX list. It is therefore best to create either a static list containing the values or an SQL list entry pointing to the table holding the AX values. This will force the user to choose an item guaranteed to match AX.
Check the required fields.
Go to https://ecmtv4-sales.caso.com/appxtenderadminAppXtender Administration site.
Enter the required credentials.
From the Menu choices choose AppXtenderDemo the appropriate AppXtender database under Application Management.
...
Choose the application the eform EForm is to write to and then choose Fields. Each project field will be shown.
...
Make note of each required field and create an EForm mapping for each one. Make the EForm question a required field so data must be entered in both the EForm and AX.
User-Defined Lists
Open the Application’s field list. Go through the fields and look for user defined list as the datatype.
...
If this is a field that will have data written to it from the EForm, go to the field properties.
...
Click on the User-Defined List button. The list entries will be shown. These are the entries that are required to be written to AX.
...
Either create a drop-down question in EForms and use the choices shown in AppXtender or create a single input question in EForms and create an SQL list in EForms dbLookups to pull the entries directly.