Next week! Join our next Tech Hour sessions on 18 and 19 December where we’ll unpack what’s new in the fresh Creatio 8.3.2 release.
Explore the latest Creatio.ai enhancements, discover new CRM capabilities apps Territory Management, and see what’s improved in Freedom UI.

Be the first to dive into the updates.
👉 Save your spot and join the session!
Register here>>>

We’re excited to introduce a new enhancement designed to help partners gain more visibility and deliver better user experiences on the Creatio Marketplace. Many listings today lack Key Features, which makes it harder for our search engine to accurately match users with the most relevant solutions. To address this, we’re rolling out AI-generated key features for listings that currently don’t have them.

How to Boost Your Listing’s Visibility

1.   Review the AI-generated key features in your Marketplace Console.

2.   Refine the text — adjust descriptions so they better reflect your solution.

3.   Add a screenshot to complete the key feature.

4.   Publish the feature to make it visible to customers and strengthen your app’s presentation.

Review AI-generated Key Features

Take 2 minutes now — this directly impacts how often your solution appears in customer searches.

Additionally, we’re introducing a manual key feature generation tool in the Marketplace Console. This capability will be available soon for all partners, giving you full control to craft or regenerate key features based on your listing data.

Let’s work together to make the Creatio Marketplace a more searchable, discoverable, and high-performing ecosystem.

If you encounter any questions or issues along the way, please do not hesitate to reach out to us at marketplace@creatio.com.

23503: insert or update on table "SysLocalizableValue" violates foreign key constraint
This issue is linked to Creatio’s localization system.

Root Cause: Redis Cache Conflict

The problem almost always comes from Redis, not the database.

If multiple Creatio environments (Dev, Test, Prod, etc.) share:

• the same Redis server, and
• the same Redis database index (DB number)

then their cached culture data becomes mixed. Creatio loads culture IDs from another environment, causing invalid keys and triggering the 23503 foreign key violation.

Solution : 

• Use a different Redis database index for each Creatio instance in ConnectionString.
• Flush the Redis.
• Restart Creatio.

Learn how to turn insights into action with Google Analytics inside Creatio.
In this 1-hour session, we’ll walk you through setting up analytics, tracking key user interactions, and leveraging data to optimize your processes and boost performance.

Perfect for marketers and analysts who want to make smarter, data-driven decisions.

When: December 3, 9:00 AM EST/ 3:00 PM CET

Join tomorrow: https://creatio-global.zoom.us/meeting/register/mLa-5as5RQO7FoweAX0CFQ

Built-in Creatio SQL Console App for Developers

Today I’m excited to share a small but very practical tool I’ve built for Creatio developers – a new in-app SQL Console for Creatio 8+.

It consists of two parts:

- Frontend (Freedom UI + Angular): A custom page with a CodeMirror SQL editor, keyboard shortcuts, a sortable & paginated Angular Material table, and CSV export. You can quickly run a query, see the result in a readable grid, sort by any column, and export data to a CSV file in one click.

- Backend (Creatio C# web service): A custom Creatio service that executes SQL through CustomQuery, logs every unique query into a dedicated table, and is protected by a system operation (CanUseSQLConsole), so only trusted technical users can access it.

There is also a hard limit of 5000 rows per query – if the result set is larger, the console returns a clear message asking you to narrow the query.

How is this different from the old Creatio SQL Console?
- The legacy SQL console package is no longer maintained or updated.
- It runs raw SQL with less control and without modern safety practices.
- This new console adds permission checks, query logging, a 5000-row limit and better UX, making it more predictable and auditable for day-to-day development work.

And how does it compare to Clio?
With Clio you usually need:
- Visual Studio Code installed,
- the Clio VS Code extension,
- Clio itself installed on your laptop.
- Error handling is also limited: when a SQL query is invalid, the extension does not show a clear database error message, so it’s harder to understand what exactly went wrong.(correct me if I am wrong 😅 )

With this SQL Console you:
- run everything inside Creatio, in the browser,
- don’t install anything locally,
- immediately see either a formatted result set, or a detailed error message from the backend, right in the UI.

A few important safety notes:
The console blocks three dangerous commands:
- DROP, DELETE, TRUNCATE will not be executed from this tool.
- There is a hard limit of 5000 records per query result.
- It’s still a powerful instrument, so I strongly recommend using it only on development (or non-production) environments.

If you work with Creatio and miss a convenient in-app SQL view, this approach might be useful for your dev stacks as well.

Github link:

https://github.com/artemivzhenko/creatio-sql-console