Hello,

he parameter “showValueAsLink: false” works only for the lookup fields on the form pages. 

 As for the Lists, unfortunately, there is no such possibility so far.

 However, our R&D team is already working on the feature that will allow disabling link generation for lookup columns of related objects, so it is expected to be implemented in future releases (no ETA yet).

Best regards,
Pavlo!

Yes, this is very much needed. Having the hyperlink is too confusing for users - most think they need to click the link to select, which just navigates away. Lookup dialogs shouldn’t have any links IMO since it’s purpose is to just select a record.  

+1 for this request...in most of my projects, this has already become a running gag :(

You can do it using Global CSS.
Install the CSS/JS Addon https://marketplace.creatio.com/app/experceo-global-jscss-editor-creatio
Then use the CSS code below:

mat-dialog-container crt-link {
pointer-events: none!important;
cursor: default!important;
}

You can improve the css selector as needed.

Hope this helps!

Thanks @Mohamed Ouederni

It's working now.

But, What values to be assigned to 'ExpGlobalJSValue' & 'ExpGlobalCSSValue' variables in system setting?

Hello,
 

You don't need to use programming for this task.
You need to create an object replacement (in your example, an Account object replacement), in which you can set the default value for the corresponding columns, save the changes, and publish the object.





 After that, when you open the pages of creating records, you will see the fields immediately filled with the default values.



These links can also be useful for you to find more options for achieving your goal:

https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platform/development-tools/creatio-ide/configuration-elements/object

https://community.creatio.com/questions/it-possible-set-default-value-f…

Thank you.

Hello Serhii,

Thank you for the reply.

1) We can not utilize the generic default value, becasue depending on the conditions the Type, might have differnetvalues.

2) Our frontend logic is associated with OpenSelectionWindowRequest. In the documentation of OpenSelectionWindowRequest there is no documentation for default values.

Is there any workaround to achieve this?
Sasor

If you need to use a value based on one of the fields of an object, it is fashionable to use business rules at the object level, which, depending on the value in one field, will set the value for another field using the “Set values” option.




 

Hello community,

any new development in the new versions of the codebase that allows us to set default values on OpenSelectionWindowRequest?

Sasor