Hello,

Unfortunately, it is currently not available to enable Multiple selections of lookup values in Freedom UI.

 

We've registered it in our R&D team backlog for consideration and implementation in future application releases. Thank you for helping us to improve our product.

Hello,

You can try another approach: the column that is responsible for the section list page that will be opened when going to the section is SectionSchemaUId (in the SysModule table). This column represents data from the UId column of the SysSchema table. What can be done to force custom page to be opened when opening the section is modifying the current SectionSchemaUId column value for the proper SysModule table record to the desired value. So you need to find the SysModule record responsible for your current section (for example using the query like:

select * from "SysModule" where "SectionSchemaUId" in (select "UId" from "SysSchema" where "Name" = 'UsrTest_ListPage')

), use an Id of the record found and then use it in the query like:

update "SysModule" set "SectionSchemaUId" = 'desired UId of the UsrPage_ebkv9e8 schema' where "Id" = 'Id found previously'

and relogin to the app after that. I recently tested it and the Services_ListPage was opened for my custom Freedom UI section:

Oleg Drobina, thank you so much! I tried this approach before and it doesn't work probably because I had a mistake with the IDs. Now it is working. Appreciate your help. Regards

Creatio 8.0.10 https://academy.creatio.com/docs/release/release-notes/8010-atlas-relea…

There is an issue in current versions of Creatio with the filter classes, such as FilterGroup etc, being applied to model load/queries. I've been reporting this issue since 8.0.6 (#SR-01182879) but it's still not yet fixed in 8.0.9, very frustrating (I've been told it will be fixed in 8.1 #SR-01198668 🤞🏻). However you can still use them with a small workaround. The example below will get all Accounts that have Type = Customer:

// make sure to add "@creatio-devkit/common" as sdk
 
const accountModel = await sdk.Model.create("Account");
 
const customerFilter = new sdk.FilterGroup();
await customerFilter.addSchemaColumnFilterWithParameter(sdk.ComparisonType.Equal, "Type.Name", "Customer");
 
// This is the workaround you have to do for the filters to work.
// Shallow copy to a new object and then reassign the items collection.
const newCustomerFilter = Object.assign({}, customerFilter);
newCustomerFilter.items = customerFilter.items;
 
// now use new shallow copied filters in the query
const customers = await accountModel.load({
    attributes: ["Id", "Name", "Type"],
    parameters: [{
        type: sdk.ModelParameterType.Filter,
        value: newCustomerFilter
    }]
});
 
// the customers variable is now an array of accounts with Id, Name, and Type columns
console.log(customers);

The whole issue with the FilterGroup is that the items collection doesn't get unrolled from a collection to an array - the copy forces the object to flatten out how it's expected by the underlying DataService call.

Ryan

Ryan = Creatio's code gap workaround master

Ryan Farley,

This is my code : 

handler: async (request, next) => {

        // Get the selected date values

        var dateFrom = new Date(await request.$context.DateTimeAttribute_6jtq65k);

        var dateTo = new Date(await request.$context.DateTimeAttribute_vg9eydm);

        var datesBetween = [];

          var currentDate = new Date(dateFrom);

          while (currentDate <= dateTo) {

        datesBetween.push(new Date(currentDate));

        currentDate.setDate(currentDate.getDate() + 1);

          }

  // Convert dates to integers without the time component

          var datesAsIntegers = datesBetween.map(date => {

        return parseInt(date.toISOString().slice(0, 10).replace(/-/g, ""), 10);

          });

        const accountModel = await sdk.Model.create("UsrEntity_a6e9b72");      

        // Load the accounts based on the filter.

        const accounts = await accountModel.load({

            attributes: ["DateTimeAttribute_x2whel6"],

        });

        console.log(accounts); 

            for (const value of accounts) 

            {

                for (const value1 of datesAsIntegers)

                {

                   const integerValue = parseInt(value1);

                value.NumberAttribute_ejh4wbq === integerValue;

                }

                console.log("1");

            }

return next?.handle(request);

        }

Here we are trying to get value of "NumberAttribute_ejh4wbq" but we are only getting "Id" .

Can you help us with this?

Verify that the column name is correct. In the accountModel.load your passing the attributes array with "DateTimeAttribute_x2whel6", this needs to be the column name in the object/table (which will likely start with a Usr)

Ryan

Hello,

Could you please describe the issue in more detail and provide the screenshots of the problem if possible?

Mira Dmitruk,

Sure !



For example, account types: we have 2 inactive values in our Account Type lookup: Our company & Contractor



In classic UI, when you work on list & form pages, these 2 values will not show up, but in Freedom UI yes (see screenshots below). Same scenario for inactive contacts, inactive accounts, inactive fields in other lookups, etc....

Any idea if this would be fixed for Creatio 8.0.10 ?

Hello!

We don`t see a column "Inactive" from our side. Could you please describe how did you create it?

Mariia Sorochan,

 

Indeed sorry, we call it "inactive" but it's deactivated records.



You activate the feature for any object by creating a replacing object, here for accounttype, and you click the OOTB feature "Allow records deactivation"







 

You will then notice the "inactive" column as a choice in the columns to display, such as the example here with a Creatio 8.0.9 trial account:







 

Did this ever get improved upon in a later version of Freedom UI?

Hello,

Please refer to this article for the detailed information. 



Best regards,

Anastasiia

Good day,

In the new interface, the details are configured similarly to the mechanism used in the old interface. It also includes automatic mapping to the ID of the current record, so there is no need to add it separately. For example, in the "Orders" detail added to the "Account" section by default, we can see that the detail displays records where Account.Id (of the current record) is equal to Order.AccountId.

Thank you for your question.

Best Regards,

Pavlo

Hello Shivani,

Standard "Notes" field will also perfectly store JSON:

So please use it to store JSON on the UI.

Best regards,

Oscar

Oscar Dylan,

Thank you for your reply. Is it possible to add another "notes" field to the table and have the value displayed in a similar manner?

Shivani Lakshman,

You can use the standard one available in any newly created section and add it to another tab if needed (but this can be done via the schema code modification directly, this option is not available in the wizard yet, but our product R&D team actively works on adding this feature to the oob functionality).

Hi Jonathan,

 

The compiling from the advanced settings UI is equivalent to compile from the Workspace console utility using the "BuildWorkspace" operation.

 

Best regards,

​​​​​​​Bogdan

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