Hello Kevin,

Thank you for your question!

Unfortunately, the list view and export are not available in the new UI for "Connected to" diagram. We've already registered this idea in our R&D team backlog for consideration and implementation in future application releases. As an option, it's possible to disable the new UI for "Connected to" diagram and get back to the old one. However, the data inserted in the new UI will be lost while getting back to an old UI, same if you decide later to change the UI to the new one, changes applied in the old one - will not be saved. If you want this to be done, please reach out to us at support@creatio.com and we will disable UseRelationshipDesigner feature for you.

Kind regards,

Anastasiia

Hello, 

Thank you for your question. 

In order to get the wanted filter please choose the correct column called "Parent account". 

Please refer to the screenshot below: 

Thank you, 

Artem. 

Artem,

Hi Artem,

the parent account field does not work correctly with the new "Relation connection" table used for describe the account hierarchy,

Hello Stefano,

Sadly, filtering will not work in this case.

It is due to the fact that the "connected to" diagram was created to be universal, it does not have any proper connections to the other objects in the system. Thus, it can't be used for filtering records in objects.

Theoretically, you can create a view table in your system where needed columns from separate objects can be added and use it in the section's filter but we don't have any examples of such implementations.

We have already created a request for our R&D team to create such functionality.

Thank you,

Artem.

Hi,

I solved the problem.
I've created a view table, here my postgres script view
 

DROP VIEW
 
IF EXISTS "UsrAccountParentView";
    CREATE
        OR REPLACE VIEW "UsrAccountParentView" AS
 
SELECT uuid_generate_v4() AS "Id"
    , reA."RecordId" AS "UsrAccountParentId"
    , reB."RecordId" AS "UsrAccountChildId"
    , rc."RelationTypeId" as "UsrRelationTypeId"
    , '410006e1-ca4e-4502-a9ec-e54d922d2c00'::uuid AS "CreatedById"
    , timezone('utc', now()) AS "CreatedOn"
    , '410006e1-ca4e-4502-a9ec-e54d922d2c00'::uuid AS "ModifiedById"
    , timezone('utc', now()) AS "ModifiedOn"
FROM "RelationshipEntity" reA
JOIN "RelationshipConnection" rc
    ON reA."Id" = rc."RelationshipEntityAId"
        AND reA."SchemaUId" = '25d7c1ab-1de0-4501-b402-02e0e5a72d6e'
JOIN "RelationshipEntity" reB
    ON reB."Id" = rc."RelationshipEntityBId"
        AND reB."SchemaUId" = '25d7c1ab-1de0-4501-b402-02e0e5a72d6e'

Solved, rights have been put on the column

i remove the rights and it is ok

Firstly you need to add the columns to the view VwContactRelationship. Please deploy the application locally and create a script that will modify the view. Then add the columns to the related object. Then the columns will appear in the section wizard. 

Hello Cristian, 

Replace the BaseRelationshipDetailPageV2 schema (and not AccountRelationshipDetailPageV2). In the BaseRelationshipDetailPageV2 schema, create a validation method for the necessary fields (e.g., validateOneOwner()). This method should return an object with the invalidMessage parameter.

Override the onEntityInitialized() method. In the onEntityInitialized() method, call addColumnValidator() for each field with specifying the validation method. Use the following article for more details: https://academy.bpmonline.com/documents/technic-sdk/7-13/how-add-field-…

An example of code is below:

define("BaseRelationshipDetailPageV2", [], function() {
    return {
        entitySchemaName: "Relationship",
        methods: {
            onEntityInitialized: function() {
                this.callParent(arguments);
                this.addColumnValidator("AccountA", this.validateOneOwner);
                this.addColumnValidator("AccountB", this.validateOneOwner);
            },
            validateOneOwner: function() {
                var message = "";
                // the needed validation
                return {
                    invalidMessage: message
                };
            }
        },
        details: /**SCHEMA_DETAILS*/{}/**SCHEMA_DETAILS*/,
        diff: /**SCHEMA_DIFF*/[]/**SCHEMA_DIFF*/
    };

Dear Heather,

To add a custom object to the connected to of the Account you would need to add corresponding record to the EntityConnection table in db with  SysEntitySchemaUid is a Uid of the Account and ColumnUId is a column uid that can be found in the SysEntitySchemaReference table. For implementing this please analyze the EntityConnection table and SysEntitySchemaReference  to have an understanding of which record you need to add. For example you can execute the following script: 
select SysSchema.Name, ColumnName, EntityConnection.* from EntityConnection inner join SysSchema on SysEntitySchemaUid = SysSchema.UId inner join SysEntitySchemaReference on EntityConnection.ColumnUId = SysEntitySchemaReference.ColumnUId

Best regards, 
Dennis 

I get this notification: Import complete. 1 of 1 records imported from the source file "AK_Relationships.xlsx".

Hello

The Relationship table has following columns: http://prntscr.com/mkwsvu

In order to import relations you need to populate the RelationTypeId, ReverseRelationTypeId, Active, AccountAId(ContactAId) and AccountBId(ContactBId) columns. Please note, that you need to fill in the columns with the precise names in order for these relations to be connected to the existing records. Else, the duplicates might be created.

Best regards,

Matt

Hello, 

If you want to create section for the new object and store Account-Contact relationships in it please follow the steps in the article below: 
https://academy.bpmonline.com/documents/technic-sdk/7-13/creating-new-s…
If by "Relationships object of bpm" you mean ContactCareer object (or other existing object) please see the article below in which you would find an instruction on how to create a section based on the existing object:
https://community.bpmonline.com/node/26247

Best regards, 
Dennis

If you're talking about the "RelationshipDetailPage" module, then yes - it's not a page. It's a module. I'm not sure if it's possible to override it correctly or not. However, you can always create your own detail and page based on the "RelationshipDetail" module and the "RelationshipDetailPage" module and use them instead of the out-of-the-box detail.