#preassigns

Hi there!

Today, I’ll show you how to preassign fieldmappings. There are three different types of preassigning values:

preassign simple values

preassign values after the usage of a defined button -  dependent on their ancestry 

preassign values after the usage of the add-button in a list -  dependent on their ancestry 

Preassign Simple Values

The first option in order to preassign a fieldmapping is that you use the field “Default Value”. If we want to preassign a yesno-fieldmapping, we have to either set yes as default value or no as default value. If we want to preassign a lookup-fieldmapping, we have to set the explicit idCodeID as default value.

Preassign values after the usage of a defined button

The second option in order to preassign a fieldmapping is that you use defined buttons. For example, we configure a button in the detailview of a person, which adds a new activity. Moreover, we want to preassign the value of the person in the activity with the person, from which we navigated from. In this option we map the preassigned values in the SQL statement and, subsequently, we define a fieldmapping of type buttoncreate.

Preassign values after the usage of the add-button in a list

The third option in order to preassign a fieldmapping is that you use the add-button in a list. For example, we want to expand the above explained example: each person has a list of activities in its detailview. Now, we also want to preassign the value of the person, when we add an activity in the list by using the add-button. Therefore, we need a statement of the type beforeNew. We map the fields, from which the mapping starts, with e.g. @idContactID, to the name of the field in the targetview, with e.g. AS idMainContactID. In the field “Field Values” we can set the names of the fields, which we want to replace with the fields, which are labelled with an @-sign. These values are separated with a semicolon.

After you configure preassigned fieldmappings, the fieldmappings should already contain content: