We deployed a custom package with several new fields added to our Contacts section, but these fields aren’t showing up in the mobile app even though they display correctly in the web interface. The fields were added through the Section Wizard and include both text and lookup types. I’ve verified the Mobile Application Wizard settings and the section appears to be included, but when users sync their mobile devices, the new fields remain invisible. We’ve tried forcing cache refresh on devices and re-syncing multiple times without success. The mobile app version matches our Creatio 7.18 instance. Has anyone encountered similar issues with custom field visibility in mobile apps? What configuration steps might we be missing for proper mobile schema updates?
Great that you got it working! Let me provide the complete solution covering all the key aspects. First, regarding Mobile Application Wizard config - you need to access System Designer > Mobile Application and select your workplace. Within the workplace settings, click on the section (Contacts in your case) to open its detailed configuration. This is where you’ll see the schema designer for mobile.
For mobile schema updates, you must explicitly add each custom field to the mobile schema. Click ‘Add field’ in the schema configuration and select your custom fields from the available columns list. Make sure to set appropriate display settings for each field - some fields might need specific mobile rendering configurations, especially lookups.
Regarding mobile cache and sync, after adding fields to the schema, you must publish the workplace to mobile. Go back to the main Mobile Application screen and click the ‘Publish to mobile’ button. This action generates the mobile metadata and updates the synchronization configuration. Without this publish step, schema changes remain in draft state and never reach mobile devices.
For offline schema inclusion, verify that your custom fields have the appropriate sync settings. Some field types require explicit offline availability configuration. In the mobile schema editor, check the ‘Available offline’ property for each field. Lookup fields particularly need their reference data configured for offline access - you may need to add related lookup sections to your mobile workplace if they aren’t already included.
After publishing, users should perform a full re-sync rather than incremental sync. Have them log out of the mobile app completely, clear app data if possible, then log back in to trigger a complete schema and data refresh. The initial sync after schema changes takes longer as it downloads the new metadata structure.
One additional consideration - if you’re using custom packages, ensure your mobile package has the correct dependencies on packages containing your custom fields. Package load order matters for mobile schema generation. Your mobile configuration package should depend on any packages that define custom sections or fields you want to display in mobile.
This combination of proper schema configuration, field-level mobile inclusion, workspace publishing, and full device re-sync should resolve the visibility issues. The key takeaway is that mobile field visibility requires explicit configuration at multiple levels, not just section-level inclusion in the workplace.
Publishing the workspace was the missing step! But I also had to manually configure the fields in the mobile schema as you all suggested. For anyone else hitting this, here’s what worked for me.
Thanks Marcus. I checked the Mobile Application Wizard and the section is there, but I’m not seeing a detailed field list. Is there a specific place where I should see individual fields listed? I’m looking at the workplace configuration screen where sections are selected for mobile access.
Another thing to verify - did you publish the workspace to mobile after making schema changes? Schema modifications require both saving the configuration and explicitly publishing to mobile devices. The publish action triggers the mobile metadata update that makes new fields available for sync.
You need to configure the mobile schema at a deeper level. The workplace selection just determines which sections are available. Each section has its own mobile schema definition that controls which columns sync to devices. Navigate to the System Designer, find Mobile Application section, and look for the schema configuration where you can specify exactly which fields should be included in offline mode. This is separate from the general workplace setup.