10,730
edits
Important: Deprecating old WebView — Publish failed error
Synchronization steps: Difference between revisions
Jump to navigation
Jump to search
→Download mobile project from CRM server
| Line 140: | Line 140: | ||
# Unpack customization.zip | # Unpack customization.zip | ||
# Check license: <code>license.ValidateEntities()</code>. This can result in an exception "LICENSE: INSUFFICIENT". | # Check license: <code>license.ValidateEntities()</code>. This can result in an exception "LICENSE: INSUFFICIENT". | ||
#: At this | #: At this point we have two customizations - old one & new one. The old is active. The new is unpacked except WWW/Images data. | ||
# Adapt database schema to the new customization: | # Adapt database schema to the new customization: | ||
#* Drop tables that were removed. | #* Drop tables that were removed. | ||
| Line 153: | Line 153: | ||
RecordQuality,636661324791448237,1,Low | RecordQuality,636661324791448237,1,Low | ||
...</syntaxhighlight> | ...</syntaxhighlight> | ||
# Unpack | # Unpack WWW/Images data. This overwrites old customization. | ||
Summary: At this moment new customization is fully activated except one thing: The app remembers that it is in process of changing the customization. Later, when the sync completes (successfully or not) and updated user interface is loaded, this transitional state will be terminated. | Summary: At this moment new customization is fully activated except one thing: The app remembers that it is in process of changing the customization. Later, when the sync completes (successfully or not) and updated user interface is loaded, this transitional state will be terminated. | ||