Feed | Community Creatio

Studio_Creatio_free_edition

06:36 Feb 17, 2026

I installed 8.3.2.4199 on my Windows with SQL Express. All worked perfectly and was able to login.

But I am getting below error when i Did first compilation without making any changes. But system is still working fine. Is there any configuration missing?

"../../CrtML/Assemblies/Terrasoft.ML.Interfaces/Terrasoft.ML.Interfaces.dll" is either a path which could not be found or it is a full assembly name which is badly formed. If it is a full assembly name it may contain characters that need to be escaped with backslash(\). Those characters are Equals(=), Comma(,), Quote("), Apostrophe('), Backslash(\).

1 comments

Dmitry S

11:49 Feb 17, 2026

This is not an error, just warning. It causes no trouble and doesn't affect a compilation result. In case you don't want to receive such kind of messages, please lower the system setting value used for displaying compilation errors / messages by yourself or ask support to do it. I believe the setting's code is CodeCompilerWarningLevel. Please try to set it to 1, by default it is 2.

Show all comments

errors

NewtonSoft.Json

compile

Financial_Services_Creatio_sales_edition

8.0

Errors After Moving Files on Localhost

Jeff Ballard

22:09 Feb 16, 2026

I have a few different Creatio instances running on a Windows server, some running PostgreSQL and other SQL Server. Everything was working fine until late last week when I moved a few things around:

Rearranged the folder structure
Removed applications from IIS and recreated them pointing to the new folder structure
Updated the connectionstrings.config to point to a different redis database
Changed the nlog.targets.config to point to the new folder structure

The database user.connection is good.

After all that, I rebooted just to make sure everything started fresh. Upon trying to log in to any of the sites/apps, I get prompted for the username & password. I would get stuck looking at the Creatio logo. Nothing would ever happen. I ask AI, and it suggests to delete the folders Pkg, Autogenerated, and Lib beneath Terrasoft.Configuration and they'll be regenerated. That yields some progress. Now when I log in, I get prompted to recompile. The recompile fails with a lot of errors - all seemingly related to the missing assembly Newtonsoft.Json:

CompatibilityMock.CrtCoreBase.cs (The type 'JsonConverter' is defined in an assembly that is not referenced. You must add a reference to assembly 'Newtonsoft.Json...)
BaseNotificationProvider.CrtCoreBase.cs (The type or namespace name 'JsonPropertyAttribute' could not be found)

I've tried dropping copies of the Newtonsoft.Json assembly anywhere and everywhere I think it might look for it:

Terrasoft.Configuration\Pkg\CrtCoreBase\Files\Bin
Terrasoft.Configuration\Lib
Terrasoft.Configuration\Pkg\CrtCoreBase\Autogenerated\Lib
It already exists in Terrasoft.Configuration\bin

And it still fails with the same error.

Any suggestions on what to look at? Where to look? This is beyond frustrating. And it's probably something simple that I'm forgetting. 🤣

0 comments

Show all comments

mobile

QR Code scanner

Mobile_Creatio

mobile sdk

Mobile_Creatio

Bluetooth Scanner Integration with Creatio Mobile?

Thomas Eva

13:29 Feb 16, 2026

Hello Everyone,

Does anyone know if Bluetooth barcode scanners can be used with the Creatio mobile app (alongside or instead of the native camera)?

I’ve seen mentions of Bluetooth scanners working with the web application on tablets, but I haven’t found confirmation of this for the mobile app. The Academy documentation only references the native camera.

Has anyone implemented this in mobile? If so, what approach did you take and were there any limitations?

Thanks in advance.

0 comments

Show all comments

Sales_Creatio

New Client Production Migration Issues

Brendan

02:20 Feb 13, 2026

We're a new client trying to get our production environment up and running with data loaded from our prior CRM (millions of records). We had been able to push updates and/or new records via the DataService adhering to the service limitations but our instance now seems to be unresponsive.

Has anyone else had this experience trying to bring in historical data? Are there any recommendations or guidance on making the process more painless?

4 comments

Ryan Farley

18:10 Feb 13, 2026

Often the unresponsiveness after loading a lot of data is due to Creatio's live update feature. Basically, many Creatio objects have live update enabled, which means for any add or update, it sends a signal back to the browser so the browser reloads the UI to show the updates/adds that occurred on the server. When loading in a large set of data, that causes a socket back to the browser for every single add or update, which the browser then reloads the data causing a request to be made back to the server to retrieve the newly added or updated data. So if you're loading a million records, that could also mean a million socket signals sent back the UI, and if your browser is open and viewing that record type, possibly a million requests to the server to load the data. All of that extra communication can cause things to get overwhelmed for large amounts of data to say the least. This feature is great for normal user activity, but when loading large amounts of data causes too much overhead. (I show below how to turn this feature off)

To get things responding again, you can restart the Creatio system which scraps all the pending socket requests. Don't do it while the data is loading, but after or when paused. I use Clio Explorer for this. Once installed and you've registered the system (also need to install Clio API package in the system which Clio Explorer can do - refer to linked article), you'll see a restart option on the menu for the registered system.

However, if the system currently isn't responding at all, you might just need to contact support and they can restart the system from their end (but for next time, this option of using Clio is quick and easy).

While you're loading the large amounts of data, you can turn off the Live Updates feature altogether. Then once the data is all loaded, turn it back on again.

To turn off Live Updates for the entire system, go to the features page https://yourcreatiosystem/0/flags then search for the feature called LiveEditing and disable it (see below). Uncheck "Is enabled" (if checked) and also uncheck for "All employees" and also "All external users" (technically, only needs to get disabled for the user you're connecting via DataService or OData with, but I just turn it off for all). Then click Clear Cache button.

Now, it will no longer add all that extra traffic with sockets back to the browser and reloading of data from the server. Then once complete with the migration you can turn that back on again.

Ryan

Dmitry S

12:02 Feb 16, 2026

Brendan,

Hi Brendan, in general the best practice is to migrate large amount of data from the source DB to creatio via DB server tools outside of the system and then use the DB prepared before implementation. If you still want (or you no other option) to do it record by record, then I agree with Ryan's advice to disable live update. The second thing is that you have to control batches length and periodicity. Couple hundreds of records in a sigle batch, and batch every 5 minutes will be ok. The third thing is to move firstly active records from the source system (for instance lately edited by the timestamp of the record itself or it's connected records, for instance payments) by some triggered event and the rest historical data normally by batch outside of business hours etc.

Damien Collot

09:31 Feb 17, 2026

Hi Dmitry, Hi Ryan,

Both excellent advice and tutorials :) (Academy could use the upgrade ;) )

what kind of db server tools do you use with Creatio ?

Dmitry S

11:47 Feb 17, 2026

Damien Collot,

for MS SQL - native SQL Management Studio and for profiling ExpressProfiler, for the Postgre SQL - JetBrains tools then :)

Show all comments

case

Lifcycle

Service_Creatio

8.0

Case Lifecycle record creation unexpectedly triggering

Hubert Pacia

15:34 Feb 12, 2026

Hello, we are experiencing unusual behavior of OOTB Case Lifecycle object. In the example below you can see a discrepancy in the dates between record 10 and 9. Record no. 10 ends at 24/09/2025 12:02 while record no. 9 starts at 25/09/2025 09:23. This creates almost a day long gap in continuity of lifecycle.

The depicted discrepancy is caused by excessive records being created at database level. These records are for the most part empty missing: CaseId lookup values that is used for list filtering, StatusId, OwnerId, PriorityId, ServiceItemId, GroupId, SolutionDate, SolutionProvidedOn.

Example of missing record from example above (minor differences due to database time zone):

This occurs very sporadically and we believe to be caused by excessive triggering of CaseSaving event in Case entity process. Specifically SaveLifecycle() method. This is consistent with change logs records. In the screen shot below is an example of expected behavior first after creation CaseSaving event and then CaseSaved event populating the fields we are missing.

Correct behavior

Example of an excessive record in change log:
Case was not modified in any of the fields fields monitored by CaseLifcycle but CaseSaving was triggered. Alongside it CaseSaved does not trigger causing missing data in the records.

Our conclusion is that CaseSaving event triggers unexpectedly under conditions that are not known to us.

This behavior has been observed in more than one independent environment meaning it is unlikely to be caused by any custom development.

If anyone has encountered such behavior I would appreciate any findings you might have on this matter.

Records created in such manner can be easily queried with command such as this:

SELECT * FROM "CaseLifecycle"
WHERE "CaseRecordId" IS NOT NULL
AND "CaseId" IS NULL
AND "CaseRecordId" IN (SELECT "Id" FROM "Case")

4 comments

Best reply

Malika

12:26 Feb 13, 2026

Hubert Pacia,

Could you please try disabling the UseCaseInSLMOldFunc feature and check whether the issue still occurs?

When this feature is enabled, the processing goes through the old business process, while the new approach relies on listeners with a clearly defined call order. With the new logic active, this kind of issue shouldn’t appear.