Время создания
Filters

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.

Like 0

Like

3 comments

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)

Ryan 

...

Hello,

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.

Show all comments
Studio_Creatio
8.0

Like 0

Like

0 comments
Show all comments
deactivate
studiocreatio
baselookup
Baseentity
Studio_Creatio
8.0

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.

Like 0

Like

1 comments

Hello 
I need to sort lookup field by custom column for mobile application.

Is it possible ?

Like 0

Like

4 comments

Hi! 

In the mobile app, lookups are sorted by the display value by default.
Sorting by a custom column isn’t available through the Mobile Wizard, but it is possible via customization using the Mobile SDK.

To do this, you’d need to:

  • Set the sort order in the mobile list settings.
  • Connect it via the Mobile Application Manifest.

Here are some helpful docs from Creatio Academy:

Mobile list customization 
Mobile application manifest

thanks but those links dont work

I need to sort lookup fields values on page, not the  list

Hello, Tomasz,

Since you mentioned a different column in your question, let's clarify the point: Do you need to change the sorting of the values in the drop-down list (from smallest to largest, from A to Z) or do you need to filter the values in the drop-down list depending on the value of another field in the related entity?

It will be great if you can describe your task and provide any screenshots that will help us understand the task.

I need to change the sorting of the values in the drop-down list by newly added column to this drop down's lookup object

By default is by name or displany name, I addred numeric column for sorting to the lookup object, I need values to be sortet by this new column's value

Show all comments

Hello,

when adding a record inline of detail list, is it possible in code to set default value for Lookup column?

Thanks.

Like 0

Like

1 comments

Here is a code sample on how I solved it, maybe it helps somebody:

handlers: /**SCHEMA_HANDLERS*/[
    {
        request: "crt.HandleViewModelAttributeChangeRequest",
        /* The custom implementation of the system request handler. */
        handler: async (request, next) => {
            if (request.attributeName === 'GridDetail_u6gv7vy_ActiveRow') {
                const activeRowId = await request.$context.GridDetail_u6gv7vy_ActiveRow;
                const gridDetail = await request.$context.GridDetail_u6gv7vy;
                const defaultType = await request.$context.UsrLookupFileType;
                gridDetail.forEach((item) => {
                    if (item.attributes.GridDetail_u6gv7vyDS_Id == activeRowId
                       && !item.attributes.GridDetail_u6gv7vyDS_Type
                       ) 
                    {
                        item.attributes.GridDetail_u6gv7vyDS_Type = defaultType;
                    }
                });
            }
            
            return next?.handle(request);
        }
    }
]/**SCHEMA_HANDLERS*/


Please change "GridDetail_u6gv7vy" name to your list name and also attribute names ("item.attributes.GridDetail_u6gv7vyDS_Id" or "GridDetail_u6gv7vyDS_Type").

Show all comments