Fixing Creatio's Auto-Generated Packages: A Precise, Step-by-Step Guide

Many Creatio developers working in Freedom UI face a common, frustrating issue: Changes made to schemas don’t save in the intended package—even when the CurrentPackageId is set. Instead, Creatio generates random packages like App_u3es9v, introduces unwanted dependencies, and bloats your workspace

6/12/20251 min read

Objective:

Prevent Creatio from auto-generating packages and assigning circular or unnecessary dependencies.

Solution: Disable UseSchemaDesignPackageUIdByHierarchy

This hidden system feature overrides your CurrentPackageId setting.
Disabling it restores control and ensures changes go into the package you’ve selected.

Step-by-Step Instructions

Step 1: Open Feature Management Page

  • Go to your Creatio instance.

  • Add the following to the URL: www.example.creatio.com/0/Shell/#Section/AppFeature_ListPage

Step 2: Search for the Feature

  • Look for: UseSchemaDesignPackageUIdByHierarchy

Step 3: Disable the Feature

  • Uncheck both:

    • Is enabled

    • Is enabled for current user

  • Click Save.

Step 4: Clear the Application Cache

  • Click the “Clear Cache” button at the top (or log out and back in).

Step 5: Set Your Target Package

  • Go to System Settings.

  • Open: CurrentPackageId

  • Set it to your desired package (e.g., Custom or your working package).

What This Fix Does

Before
New random packages auto-created
Circular/unnecessary dependencies added
Ignored CurrentPackageId setting

After
Changes go to the package you selected
Clean, controlled dependency structure
Full respect of your selected package

Pro Tip:

Make sure your target package is:

  • Unlocked in the current environment

  • Installed and active in the system

Otherwise, even with the fix, Creatio might default back to auto-generation behavior.

Final Notes:

This approach is ideal for:

  • Devs working on modular custom packages

  • Teams using Dev > QA > Prod pipelines

  • Avoiding the junk package mess and dependency hell