Cannot Load a Layout
On this page
7.4 Cannot Load a Layout
Separate unreadable files, incompatible software, policy, and sync failures from missing external resources.
7.4.1 Identify File Type
.skdCard is a card layout, .clcf a server-dependent synchronization configuration, and .repx a report template. Databases, application requests, and exports are not card layouts. Show extensions in Explorer and check HTML downloads, double suffixes, incomplete attachments, size/time/source. Obtain an original copy rather than renaming extensions. Same filename does not mean same release; inspect copies without overwriting originals.
7.4.2 Missing, Damaged, or Incompatible Files
Check changed shares/drives/sync paths and do not create empty same-name replacements. Request redelivery for zero-byte/interrupted/unknown files. Preserve known-good and failed copies separately and use matching official software, not old individual components. One failing layout suggests a targeted designer investigation; all layouts failing also requires 7.1-7.2. Do not repeatedly save over the only original.
7.4.3 Passwords, Policies, and Resources
Use the layout's role and COC permission. Designers must save/republish policy changes; local setting deletion does not override embedded rights. If the layout opens but elements fail, inspect database/query fields, photo paths, fonts, and interfaces. A layout backup does not contain all external data. Missing fonts affect wrapping/size; missing photo sources leave blanks without proving corruption. Record the element/source instead of redesigning the whole card to mask the environment.
Figure 7.4-1. Show English extension-visible demonstration files and an authentic redacted loading state. Distinguish skdCard/clcf/repx, size/time, and hide private paths/data/policies.
7.4.4 Synchronization Fails or No New Release Appears
Check licensed function, sync database, title, table, and content/version fields. Share access is not sync-database access. The publisher must save the actual new layout to the database, not only .clcf settings. Clients compare versions, not local timestamps; do not edit versions to force downgrade/bypass checks. With output paused, retry normally and verify actual title/design/data connection. Loading an old local file is not synchronization success. Delete/change the entry only for an approved switch to manual mode.
7.4.5 Restore a Default and Accept
Open the verified file, check user/scope, sides, photos, and one sample before setting default. Close/reopen and confirm the intended layout/mode. Setting ordinary skdCard as default can disable synchronization. Record application/layout/release/data target and review old policies, mappings, and print rules before restoring earlier artwork; appearance alone does not establish current behavior.