App projects: Difference between revisions

Jump to navigation Jump to search
Line 177: Line 177:
=== Managing fields ===
=== Managing fields ===


After enabling an entity, you can select fields that you plan to use on this entity in the Resco Mobile CRM application. For example, you can pick some additional fields you want to use in your mobile project: City, Country/Region, Street and ZIP/Postal Code. Here you can also enable the custom fields for the entity.
After enabling an entity, you can select fields that you plan to use on this entity in Resco mobile apps.
* To enable a field, select the checkbox in the field's row and click '''Save'''.
* To disable a field, clear the checkbox in the field's row and click '''Save'''.
* Some fields are mandatory and cannot be disabled.
 
For example, you can pick some additional fields you want to use in your mobile project: City, Country/Region, Street and ZIP/Postal Code. Here you can also enable the custom fields for the entity.


{{Note|Best practice: We recommend not to include too many entities and fields in your mobile project. Backend servers often include a large wealth of entities and fields, and most organizations only use a small subset. An even smaller subset of the data is necessary in the field. [[Sync Filter]] can further restrict which records should be downloaded to the mobile device. Careful planning can improve the performance of the app and satisfaction of the users.|Tip}}
{{Note|Best practice: We recommend not to include too many entities and fields in your mobile project. Backend servers often include a large wealth of entities and fields, and most organizations only use a small subset. An even smaller subset of the data is necessary in the field. [[Sync Filter]] can further restrict which records should be downloaded to the mobile device. Careful planning can improve the performance of the app and satisfaction of the users.|Tip}}

Navigation menu