You could add a business rule at the object level to disable editing of the email, but then it would also be disabled at the page level (unless that is also what you want). Other than that, the only option is to turn off the editable list property (since, currently, you can't make certain fields editable and others not)

@sasori Great idea !

Try add a readonly flag to your column in crt.DataGrid for Contacts
After that try to restore default settings on the page for this detail if you added more columns to this grid. This functionality is kinda buggy.

That is implemented in BaseAddressEventListener. It’s basically an entity event listener class. See more about those here: https://customerfx.com/article/adding-code-to-listen-for-entity-events-in-creatio/

Ryan

Obviously, you can do that pretty easily with a process too. 

I imagine that I'll also have to code in the fact that it's non-editable?

That is just a rule at the object level

Ryan

Hi Community,

Any update regarding this scenario?

Sasori

Sasori,

You can fetch the event of deletion in a business process. Then you can do actions and if your object opportunity has live update set then the updates will appear as soon the business process has run.

Other option would be to add your own action in the list and handle all necessary changes in the page.

Franck

Hello!

There is a crt.DeleteRecordsRequest, you can add a custom handler for this request (handlers in schema metadata).

This request is called when the user tries to delete records from the row menu and bulk actions menu.
But it is called before user confirmation (modal window), and rights checking.

There are such properties in the payload: 

dataSourceName - data source name of list, for which request is called;
filters - filters for records deletion(passed when records deleted by bulk actions panel)

recordIds - record ids which should be deleted (passed when record deleted by clicking row menu delete button)

Example:

handlers: /**SCHEMA_HANDLERS*/[{
            request: "crt.DeleteRecordsRequest",
            handler: async (request, next) => {
                const dataSourceName = request.dataSourceName;
                const filters = request.filters;
                const recordIds = request.recordIds ;

                console.log(dataSourceName, filters, recordIds );
                return next?.handle(request);
            }
}]/**SCHEMA_HANDLERS*/,

Hello Kumar,
Looks like this task is impossible for now because Freedom UI doesn't allow getting the value of one control (attribute) in the code of custom validator for another control.

We have this task registered on our R&D team and will get this possibility in future releases, please follow the updates.

Best regards, Anhelina!
 

Hello Sasori,

unfortunately, it is quite difficult to analyze the issue like as there might be too many different reasons for such an error.

I kindly recommend you creating a separate support case and our team will help resolving the problem you are facing.

Kind regards,

Gleb.

Thank you Gleb :)

I was having similar issues.  What I found out is it depends where the detail is at.  For example I was creating a detail around work history.. One of the default fields was contact.  If I entered any contact other than the employee I was looking at it wont show on that contact record.  There is a logical dependency there...  I took the contact component out and works fine....  @Sasori... that is My guess as to what you are running into.

Jason Miller,

Thank you very much Jason !

Hello Jeremy, 

You can add the chart for the Account's section record, it will be available once the record page is opened. It can be done through the Section wizard same way as you add a new column, just choose the needed page element.  

Also, you can create a chart for the section here:

Inserting the chart in the list view of the standard section, however, will require additional development. 

Best regards,

Anastasiia

Unfortunately at the moment, Business Rules don't work with details with the editable section.

We have already registered a problem to fix it in future releases. I attached this case to increase its priority.  

Михайло Зеленюк,

Yes this is a very important ask, suddenly changes can be made that were not before.



Thanks,



Damien

You can lock the fields in the editable detail using business rules on the page for the detail, rather than in code. On the page for the detail, add a business rule to make the field not editable. Something like 

Condition: Boolean true = Boolean false (something that is never true)

Then: Make field editable (the condition is never true, so field is never editable)

The business rule will apply to the detail list and the fields will not be editable in the detail list.

Ryan

Hi Ryan,

I'm actually working with the BaseGridDetail so I can't lock it with a business rule... do you have any other idea?

Thanks anyway.

Luca

Luca Tavasanis,

IIRC to do it in code I usually do it like this (but unable to verify if this is correct at the moment)

getCellControlsConfig: function(entitySchemaColumn) {
    // get config from base 
    var config = this.callParent(arguments);
    var columnName = entitySchemaColumn.name;
 
    // if this is the column I want to disable
    if (columnName === "UsrMyColumn") {
        Ext.apply(config, {
            enabled: false
        });
    }
 
    return config;
}

Hopefully that gets you closer, of course, if you're wanting to disable all, you could just remove the if to check the column it's for.

Ryan

Ryan Farley,

I just tried what you suggested but unfortunately it's not working... it returns an error when I use this.callParent(arguments);.

Thank you anyway.



Luca

Luca Tavasanis,

While I was debugging I have noticed that the properties of the labelConfig that enabled some of the fields where added in the method: "applyBusinessRulesForActiveRow: function(id, gridLayoutItems)" and to fix the issue I just added this method in the client module.

Hello Yosef,

I have an article outlining how to do this here https://customerfx.com/article/adding-an-edit-button-to-the-selected-ro…

Hope this helps. 

Ryan

Ryan Farley,

Works like a charm!

I do however recommend adding the following for consistency:

{
  "className": "Terrasoft.Button",
  "style": this.Terrasoft.controls.ButtonEnums.style.TRANSPARENT,
  "tag": "edit",
  "markerValue": "edit",
  "imageConfig": {"bindTo": "Resources.Images.CardIcon"}
},

This way you get the same icon as the other details.

Kind regards,

Yosef

Yosef,

That is true, I do have that in the article as well (it's at the end of the article), however at the time I was doing this for a system where they wanted the "edit" action more obvious to users. However, for consistency with the rest of Creatio, I'd go the route of using the icon as well.

Glad it worked for you.

Ryan

Hello Amritha,

To add more columns to the "Columns setup" they should be added to the detail object directly and then they will become available in the "Columns setup". Starting from 7.16.4 horizontal scroll in the column setup is available out-of-the-box so please update your app to 7.16.4 to get needed functionality without additional development. As for adding the scroll to the main detail - I am not sure if it is possible since properties like "overflow-y" or "scroll-padding-top" are CSS properties that can be theoretically added to the grid wrap of the detail data grid, but it would be easier to use the "Show more" option at the bottom of the detail rather than developing custom CSS and connecting it as a separate module to the detail schema.

Best regards,

Oscar