#mobileviews

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:

Hi there!

Today, I'll show you which mobileviews are provided to configure your app:

advancedlist, advancelistedit: This view represents entries in a list. If a normal list is not sufficient due to a high number of entries, you can use the advancedlist to be able to handle an efficient management of your data.

cache: A cache list allows you to store entries temporarily.

calendar - list: This view stores entries, which are ordered by date.

calendar - scheduler: This view allows you to graphically store your entries containing a date. You can either choose day view, week view, month view or year view.

chart: This view represents data in either pie diagrams, bar diagrams, donut diagrams, funnel charts, bubble charts, line charts or area charts.

dashboard: This view allows to represent different views within one view.

detail: This view shows detailed values about a selected entry.

documentlist: This view allows to represent documents in customary formates, e.g. PDF.

formular: This view shows detailed values about a selected entry. Compared with a detailview, the formularview allows the user to change values within the same view.

gauge: This view can be used to display a value.

list, listedit: This view represents entries in a list.

map: This view displays entries on a map - provided that an address is available.

multirowlistedit: This view represents entries in a list, which can be edited directly within the view.

shortcut: This view shows detailed values about a selected entry in a list after a long press on the entry.

sync: This view provides the synchronisation of data.

tile button: This view is represented as button, which is customizable and which you can use in dashboards, detailviews and formularviews.

web: This view shows a website - either static or dynamic.

Hi there!

Besides filters in lists, we can use filters in the searchfields of lists, if searchfields are defined. So, now I'll give you an example how the filtering works in searchfields of either listviews or calendarlistviews.

As mentioned above, it is important that the search is defined, i.e. you have to state the searchfields, for instance: searchfields=name,company. Then we do need fieldmappings in order to set the filters. We configure the fieldmappings displayed in the following screenshot. 

For each fieldmapping, which should be a filter in the search, we have to set the definition isFilter. If isFilter=yes is set, we can use this filtering. For example, if we want to search in the project list for all projects of one specified company, we can set the name of the company within the filter.

If you click on the right button within the searchfield, the filters are shown.

Hi there!

Today, I'll show you an example how to configure filters in listviews resp. calendarlistviews. For example, we want to differentiate between all projects, next projects and critical projects by adding filters. In crmclient online, we provide the field "Search", where you can configure filters.

You can add a filter by simply giving the name of the filter and stating the SQL statement. Please be aware that you have to separate the name of the filter and the SQL statement with a semicolon. In the following, I'll show you the pattern for generating filters:

Alle; NameOfFilter1; SELECT ... FROM ... WHERE ...; NameOfFilter2; SELECT ... FROM ... WHERE ...; ...

The keyword Alle indicates that all elements you selected in your normal SQL statement are shown in the first filter section. After this section you can start with your new filters.

After configuring the app, your filters are available in the list after clicking the upper right eye button, which is just visible if filters are defined.