Start a conversation
  1. ACRM Support
  2. ACRM - Articles
  3. Public Articles

Resolving Configuration Import Issues in Aurea CRM

Overview

The issue involves the silent ignore of changes during configuration import in Aurea CRM, version 15.24.2.3163. The error occurs when using "Upload package into configuration" with exports that lack necessary package metadata, leading to uncommitted changes. This behavior is observed across all configurations, including ARZ_TABLET. The correct procedure involves aligning export and import modes and ensuring a single configuration context to avoid errors with multiple configuration IDs.

Solution

Follow these steps to resolve the configuration import issues in Aurea CRM:

  1. Verify Export and Import Modes:
    • Use "Upload configuration" for full configurations with all necessary files.
    • Use "Upload package into configuration" only for packages with required metadata like PORTAL_BULKLOAD.xml and CONFIGVERSION.xml.
  2. Ensure Single Configuration Context:
    • During export, ensure only one configuration context is selected to avoid multiple configuration IDs in TMP_PORTAL_CONFIG.xml.
  3. Diagnose Silent Ignores:
    • If using "Upload package", ensure the export includes all necessary package metadata.
    • Confirm that the import mode matches the export type to prevent silent ignores.
  4. Handle Multiple Configuration IDs:
    • Review export options to ensure a single configuration context.
    • Manually edit TMP_PORTAL_CONFIG.xml to retain only the desired configuration node if necessary, but this is not officially supported.
  5. Verify Designer Packages for Mobile/Tablet:
    • Ensure packages include all related elements as separate XML files and required metadata for successful import.

Note: For advanced scenarios or undocumented behaviors, consult Aurea support for guidance.

Frequently Asked Questions

1. How do I ensure my configuration export is correctly structured for import?
Ensure the export includes all necessary configuration and metadata files for "Upload configuration" or package metadata for "Upload package into configuration".
2. What causes the silent ignore of changes during import?
This occurs when using "Upload package into configuration" with exports lacking required package metadata, leading to uncommitted changes.
3. How can I resolve errors with multiple configuration IDs in TMP_PORTAL_CONFIG.xml?
Ensure a single configuration context during export to avoid multiple configuration IDs, and consult Aurea support for further guidance if needed.
Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Priyanka Bhotika

  2. Posted

Comments