Adding user_def fields

Hi Ramya,

if the amount of the existing user def fields are not enough, you need to create an extension table.

Example for Request:

Create new Custom Metadata C_Extension_Request1.

After that ,you need to create the relationship.

One remark, fields of an extension table will not be displayed on the mobile client. Therefore you might need to change the baisc user def field information with some of the extension table.

Best regards,

Sven 

Hi Ramya,

the mobile client can only work with fields from the basic table.

You have two options to reflect the new required field on the mobile client

1. You need to rearrange the existing fields 
   1. example: you have used an user def field for an special sales number which should be visible on the web client but not necessarily on the mobile client. Then you need to use the user def field from the extension table for this number and so on
2. You can create a custom table and create a parent relationship table with the request table. Any fields of the custom table can be reflect on the mobile client. But in this case the key field need to be custom key field like an internal automated id

This is by the way the same for an new custom status which should be visible on the mobile device. This will be only visible on the mobile client if the task has been already sent to the mobile client. But not if this is the first assignment to the mobile client.

Hope this helps Ramya :-)

Best regards,

Sven

Apart from the limitations for the mobile client, the additional fields added this way are also not useable in sorting/ordering the list view of the primary table.