Vendor-Specific Integrations

When configuring the Algolia Marketplace app, the "Index" dropdown is empty or returns an error.

Resolution

1. Verify the Algolia API Key and Application ID provided in the app settings.
2. Ensure the API Key has "List Indices" permissions in the Algolia dashboard.
3. Check if the index was recently created; it may take a few minutes to appear in the API response.

The dropdown correctly lists the available Algolia indices.

Integrating RWS Trados in a stack may fail when the master language is set to a generic locale not supported by the vendor. This prevents the selection of source content for translation projects.

Root cause

The third-party translation tool requires region-specific language variants (such as en-us) and does not recognize generic root locales (such as en).

Resolution

1. Create a new regional language variant, such as English - United States (en-us), within the stack settings.
2. Configure the generic master language (en) as the fallback for the newly created regional locale.
3. Select the regional locale when initiating translation projects through the Trados app.

After creating the regional locale with a fallback, navigate to the Trados app and attempt to select the language.

If the language appears as an available option and allows project creation, the mismatch is resolved.

Creating a translation project in the Trados Marketplace app may fail with disabled buttons or "Item not found" errors when source entries are not properly grouped. This prevents the initiation of translation workflows for selected content.

Root cause

The integration requires source entries to be associated with a specific Contentstack release that must be selected within the plugin UI to enable project validation.

Resolution

1. Create a new release within the Contentstack stack.
2. Add all entries from the source locale that require translation into this release.
3. Navigate to the Trados plugin dashboard and select the created release from the dropdown menu.
4. Enter a unique name for the target translated release in the "Create Release" field.

After selecting the source release and providing a target release name, check if the "Create Project" button becomes enabled.

If the project creation proceeds without "Item not found" errors, the release-based workflow is correctly configured.

Configuring the Salesforce Commerce Marketplace app may result in a disabled save button and "valid inputs" validation error when credentials are incomplete. This prevents the storage of integration settings within the stack.

Root cause

The app performs real-time client-side validation, blocking the save action if required fields like Organization ID or Site ID are missing or if the Client ID does not match the Short Code.

Resolution

1. Navigate to the Salesforce Commerce app configuration page.
2. Enter all required fields: Client ID, Client Secret, Organization ID, Short Code, and Site ID.
3. Ensure that the Client ID specifically corresponds to the Short Code provided by the Salesforce environment.
4. Verify that the SLA key is set to private and generate a new secret if the current one is invalid.

After entering all required credentials correctly, hover over the Save button in the app configuration.

If the "testConfig" error message disappears and the Save button becomes clickable, the validation is satisfied.

Adding a new configuration in the Salesforce Commerce connector may fail with a duplicate ID error when the same Site ID is reused. This prevents the setup of multiple environments within the same stack.

Root cause

The connector enforces a strict uniqueness constraint on Site IDs, prohibiting the use of the same ID across different configurations even if they utilize different client IDs or environments.

Resolution

1. Identify the existing configurations within the Salesforce Commerce app to see which Site IDs are currently in use.
2. Contact the Salesforce Commerce Cloud (SFCC) administrator.
3. Request the creation of unique Site IDs for each distinct environment (e.g., staging, production).
4. Enter the new, unique Site ID in the configuration fields in Contentstack.

After obtaining a unique Site ID, attempt to save the new configuration in the Salesforce Commerce app.

If the "Duplicate site id" error does not appear and the configuration saves successfully, the unique ID requirement is met.

Integrating multiple Shopify stores may trigger a 40KB size limit error when syncing large product datasets to an entry. This prevents the saving of entries containing extensive third-party product metadata.

Root cause

The error occurs because the integration attempts to store the entire Shopify product JSON payload in a single field, which exceeds Contentstack's strict system storage constraints.

Resolution

1. Navigate to the configuration page of the Shopify custom field within the content type.
2. Review the data mapping settings to identify the fields currently being synchronized.
3. Select only the specific fields required for your implementation (e.g., product title, SKU, or price) instead of the full dataset.
4. Save the field configuration to reduce the total payload size stored within the entry.

After limiting the stored fields, attempt to select a product from the Shopify store and save the entry.

If the entry saves successfully without a 40KB size error, the payload is correctly optimized for system limits.