Basic functionality doesn't include the ability to apply filter conditions based on the connected objects for the portal user directly in the section, therefore the advanced filter option is not available for such user there.
As a workaround you may use a dynamic folder and set the needed filter conditions for it.
Also, we already have a query registered for our responsible R&D team to implement this functionality for portal users in the upcoming versions of the application. I will assign your case to this project in order to increase its priority.
Note, if the tab contains both details and field groups, there's no need to refresh the details independently since using this.reloadEntity() will reload both the field groups and the details on the page.
Unfortunately, your task cannot be achieved by using OOTB tools.
Business rules functionality can be used for "Connected to" detail only for filtration. But sadly, other rules will not be applied to this detail.
We have already registered the corresponding query for our R&D team and will be waiting for the implementation of this functionality in future releases.
I wanted to change the default field on the filters in the section page to other field, but right now it shows only the display value field. How can we achieve it?
The field displayed as first in the filter is the object displayed value. You can change it in the object itself via configuration in object properties.
Have a functional conflict with this implementation. Lets say, I have an object called Application with 2 columns - Application Number and Application Name.
What it is noticed is, if we set the filter default to Application Number, then the Title in the edit page of Application is also set to Application Number but as per the requirement, we want the title in edit page to display Application Name. How can we achieve it?
Inshort, how can we separate out the functionality - ie.,
1. To have the filter default to Application Number
2. To have the Title in Application Edit page set to Application Name
Unexpected issue in MSWord prugin for printables. Happens when I try to Select report. I assume this happens when printables/reports are trying to be loaded
Unexpected character encountered while parsing value:<. Path"", line 0, position 0.
This error indicates that one of the reports has the lookup column which has no parent object specified. In order to clarify which report exactly has such column you may delete the reports one by one, each time checking whether the issue is reproducible after deleting the specific report (I'm afraid it's the easiest way).
Once you have clarified which report gives an error and which lookup column doesn't have the parent object, there is a need to run the following query for the object of this lookup column:
update [SysSchema] set [ParentId] = (select [Id] from [SysSchema] where [Name] = 'BaseLookup') where [Name] = 'The name of the object with an error (not its Caption, but Name)'
After that the issue should not persist for this report.
I have scenario where I want to update a particular detail table to the user once the background process finish to show newly added entries in that detail.
Basically, the process needs to send a message back to the client. The client listens for this message on the page, then when received, refreshes the detail.
Basically, the process needs to send a message back to the client. The client listens for this message on the page, then when received, refreshes the detail.
We are looking for a for a way to impose a character limitation on a string value that is different than the standard settings.
For example, the user enters a job number as a string and we want to restrict entry to only 10 characters. Is there a way to do this? Obviously not OOTB but with some customization?
I am trying to apply a default filter to a detail from the client side. The filter works fine using a function declared in the filterMethod property of the detail. The problem with this approach is that the filter that I applied is not visible.
The task implementation must have the following display.
Is there a way to show the filter that I applied from the client side (js) like the example above.
We have a requirement to add attachments in mail by reading the attachment from a custom attachment detail. To achieve this, we are using a Send email with attachments Marketplace application.
The issue with the above application is, it is getting installed successfully. But when accessing the element in business process its settings is not opening also getting some error in the console. (refer the screenshot attached)
We are aware of this issue. R&D department fixed this bug in version 7.18.4. If you have an earlier version of the application, we recommend updating it to the current version.
We have a case where we import bulk data into many sections. Is there a way to prevent records from being imported if a given lookup is not present in the master lookup table?
Example : Salutation (Title) has the following values : Mr. Dr. Ms Mrs.
During excel import, if column has Miss, we don't want that record to be added. Can we restrict this through object permissions or any other way?
I understand as per the documentation (pasted below), new values will be added. Is there a work around to prevent this, given that the data import is quiet big?
Be aware that lookup values not found in Creatio will be created automatically. When checking the values, the opening and closing spaces and letter case are not taken into account, while special characters are important. For example, if the imported file has the "customer" value and the [ Contact types ] lookup contains the "Customer" value, new values will not be added to the lookup and the record will be linked to the existing lookup value. However, if the “Client” contact type is specified in the import file, a new “Client” value will be added to the [ Contact types ] lookup. To avoid duplicates in the Creatio lookups, check the lookup values in the imported file.
Unfortunately, are no such basic tools for imported records.
1) You can create a business process that will modify\remove data that was created on the exact date (since after data import is finished all imported records receive a similar "Created On" value). You can use this value when finding needed records.
2) Records that are imported are tagged using the "Data import" tag and you can use this tag when building a process to find imported records. With the required condition.
You can use one of those ways to find imported records and after that apply changes to those records using the business process that is needed for your business task.
This really needs to be an option in the data import, and lookup value automatic creation should be off by default, potentially with the option to blank the lookup if no match found or fail the import (which I think should also be the default). It's quite a dangerous thing to have an OOTB import feature that defaults to creating potentially bad data in the system.
.jpg){kind=avatar}
