We are transferring our package from dev to prod site and package migration is successful but source code files are not transferred from dev to prod -
In dev site there are total - 35 source code files
But in prod only - 25 files.
Package migration is not throwing any errors its always successful but when I see the application hub I noticed that it only shows package with timestamp till 12 June 2025
Can you please help us why is this happening in the system?
Is it possible to write a row (to the bottom) of an Excel spreadsheet from Creatio?
We need to copy select data from a Creatio screen to a row on a spreadsheet. In our case, the spreadsheet lives on a Sharepoint drive. The goal is for the user to push a button on a Creatio screen, and have it insert data to the last row of an existing spreadsheet.
Any direction or suggestions you have are appreciated. Thanks! Rob
I have something like that working (except I am using a hosted Google Spreadsheet) that is using make.com. I just execute a Make.com webhook from a process in Creatio, make.com receives that and then writes the line to the existing spreadsheet. All no code, so just thought I would mention.
Thanks. However, we are not using Google Sheets, our corporate standard is Excel / MS Office. Creatio would need to integrate with an existing spreadsheet used by our Operations department -- Is there a connector for that too?
Can anybody help me with this error message please?
I created a new campaign and upon saving I had this message.
There are marketing emails attached to the campaign. They were automatically assigned a start date (which I cannot edit) that is the same as the creation date. So it's in the past - could this be why I'm getting this message. All other fields are filled out and look correct.
This is a bug in Creatio. Contact support and they can apply a fix to your system. If needed, you can have them refer to the case I opened on this #SR-01400125.
Essentially, there's a bug that incorrectly checks the dates for trigger emails (since trigger emails don't need a start date as they're started from the campaign)
Thank you for reaching out. Ryan is absolutely correct.
This issue has been identified and a fix will be available in the upcoming Creatio 8.3.1 release. Once that version is available, you can update your site to resolve the error.
Alternatively, if you'd prefer not to wait, you can request that the fix be applied to your current version by contacting our support team directly.
Hey Community I’m trying to enable record deactivation on an object that inherits from BaseEntity. The object is also used as a lookup in several other objects. From the documentation it looks like the “Allow records deactivation” option is only available for BaseLookup objects.
Has anyone found a reusable approach—perhaps a utility class —that lets a BaseEntity behave like a deactivatable lookup? I’m aware I could add an IsActive Boolean column, but that would require adding filter logic everywhere the object is referenced, which I’d rather avoid.
Any pointers or examples would be greatly appreciated.
