The Copy App feature in SearchStax Site Search copies configuration settings from a source App to a destination App. You can use it to test changes in a non-production App before copying the configuration to a production App.
Copy App overwrites configuration in the destination App. It doesn’t merge the two Apps or copy indexed content.
Before You Copy an App
Before you start:
- You must be an Owner or Administrator.
- Copy App must be available for your account. If you don’t see the Copy Application action, your role or account might not include access to the feature.
- You need both a source App and a destination App. Copy App doesn’t create a new App. If you need a destination App, see Creating Your First Search App.
- The source and destination Apps must use the same platform.
- The destination App’s schema must be compatible with the source App’s schema.
- Copy App overwrites configuration in the destination App. You can’t undo the copy.
- Copy App doesn’t change who can access the destination App.
- Copy App doesn’t copy indexed content from the source App. Content already indexed in the destination App remains there.
Schema Compatibility
The destination App can have fewer fields, field types, or dynamic fields than the source App.
However:
- The destination App can’t contain schema definitions that are missing from the source App.
- If a field, field type, or dynamic field exists in both Apps, its definition must match.
Copy App replaces the destination App’s configuration, including its schema. Site Search checks schema compatibility before the copy to prevent the operation from removing or changing schema definitions that the destination App might already depend on.
If the schemas aren’t compatible, the error message lists up to 10 fields or field types that need attention.
What Copy App Changes
Copy App copies these settings from the source App to the destination App:
- Languages, including custom language associations and App-level language settings
- Search Profiles
- Synonyms
- Auto-Suggest dictionary
- Related Searches dictionary
- Search Fields
- Results Fields
- Facets
- Ranking
- Spell Check dictionary
- Stopwords
- Data Filters
- Location
- Rules
- Sorting
Copy App doesn’t copy:
- Access Management settings
- Crawler configuration
- Indexed content
- Promotions from the source App
- Smart Match Assist recommendation data
Copy App does preserve the source App’s Smart Match Assist enabled or disabled setting. After the copy, the destination App uses the same setting.
Auto-Suggest
If the source App has Auto-Suggest enabled, Copy App checks whether Auto-Suggest is ready in the destination App.
If Auto-Suggest isn’t ready, Site Search starts setting it up in the destination App. Wait about 10 minutes, then run Copy App again.
Promotions
Copy App never copies Promotions from the source App to the destination App.
How it handles existing destination Promotions depends on the Search Profiles in the two Apps:
- If a Search Profile with the same name exists in both Apps, the destination App keeps the Promotions associated with that Profile.
- If a destination Search Profile doesn’t have a matching Profile in the source App, its Promotions are removed as Copy App updates the destination configuration.
Copy App doesn’t merge source and destination Promotion lists.
Copy a Search App
To copy an App’s configuration:
- Go to the All Apps list at the top of the Site Search navigation menu.
-
Click Copy Application beside the source App.
-
Verify the source App. Select the destination App.
If the App uses multiple languages, select the languages to transfer.
Review the destination carefully. Copy App permanently overwrites its configuration.
Click Next.
-
Review the Copy App request.
Confirm that the source and destination Apps are correct, then click Copy App.
-
Wait for Site Search to finish copying the configuration.
A green banner confirms when the copy succeeds.
Troubleshoot Schema Compatibility Errors
If Copy App fails because the schemas aren’t compatible, Site Search lists up to 10 fields or field types that need attention.
Common causes include:
- The destination App contains a field, field type, or dynamic field that doesn’t exist in the source App.
- A field exists in both Apps but uses different settings.
- A field type exists in both Apps but has different definitions.
- A dynamic field exists in both Apps but has different definitions.
The error might not show every mismatch at once if more than 10 differences exist.
Compare the Schemas
- Open the source App and destination App.
-
Use Reload Schema in both Apps.
Reloading the schema refreshes the fields Site Search displays from the current schema. It doesn’t change schema definitions or make the two schemas compatible.
-
Review the fields or field types listed in the Copy App error.
If the destination contains a definition that is missing from the source, determine why the Apps differ. For example, an indexing pipeline, Crawler configuration, or CMS/DXP connector might have created fields in one App but not the other.
-
Make the schemas compatible.
The source schema must include the definitions required by the destination. Definitions that exist in both Apps must match.
If the affected definitions aren’t visible in the Site Search Dashboard, you can use the Schema API to compare them. You need a Read/Write token for each App. See Upload Configurations for Schema API access requirements.
If you can’t confirm or safely correct the schema differences, contact Support.
- Run Copy App again after the schemas are compatible.
If you still can’t resolve the error, contact Support. Include:
- the source App name
- the destination App name
- the fields or field types listed in the Copy App error