Efficy Overflow Q&A - Recent questions tagged relation

problem occurs when deleting a relation link (Prod_Case)

Thu, 07 Jul 2022 15:44:22 +0000

Hello,

I have a problem when I'm trying to delete the relation PROD-CASE :

In the function deleteRelation, the detailKey return keyProd-KRelation

It displays this error :

There is a custom that has been added in the field (K_RELATION)

Which tables I need to check to make the delete relation works ?

How to add Documents, tasks, products, opportunities, cases, mails to a Step like if it was into Stage.

Fri, 23 Oct 2020 09:32:36 +0000

I need to link documents, tasks, products, opportunities, cases, mails to a Step like if it was into a Stage.
I added a new tab products on stages and it work sot the method to attach tables is ok, but no one of the tab is working when I call a step. I saw that some of WkldEditDetailTabHeaders and WkldEditDetailTabContents was filter by <# if (!isStep) { #> or <# if (isStep) { #>

So in my custom I changed some stuff to make it appear and I created a variant of the addLink button to have
data-msg="addLink;WrkStep;<#=@ data.key #>;$detail$" or data-msg="addLink;WrkStag;<#=@ data.key #>;$detail$" both (WrkStep and WrkStag) are existing into the sys_tableviews.
Why it has no effect on addLink for steps while it work's on step. I call only a basic addLink.

Into MacroWorkloadCustom I changed the standard like this.

For main entity commnands :

WkldEditDetailTabHeaders {[WkldTabHeaderFields;WkldTabHeaderMemo;WkldTabHeaderActi;WkldTabHeaderCase;WkldTabHeaderDocu;WkldTabHeaderMail;WkldTabHeaderOppo;WkldTabHeaderProd]}
WkldEditDetailTabContents {[WkldTabContentFields;WkldTabContentMemo;WkldTabContentActi;WkldTabContentCase;WkldTabContentDocu;WkldTabContentMail;WkldTabContentOppo;WkldTabContentProd]}
WkldDetailGridColumns..Prod {[MENU2,NAME]}

For workload MicroTemplate :

WkldTabHeaderActi   {[<dd><a href="#tab-acti" class="i-Acti" draggable="false"></a></dd>]}
WkldTabHeaderCase   {[<dd><a href="#tab-case" class="i-Case" draggable="false"></a></dd>]}
WkldTabHeaderDocu   {[<dd><a href="#tab-docu" class="i-Docu" draggable="false"></a></dd>]}
WkldTabHeaderMail   {[<dd><a href="#tab-mail" class="i-Mail" draggable="false"></a></dd>]}
WkldTabHeaderOppo   {[<dd><a href="#tab-oppo" class="i-Oppo" draggable="false"></a></dd>]}
WkldTabHeaderProd   {[<dd><a href="#tab-prod" class="i-Prod" draggable="false"></a></dd>]}

WkldTabContentActi {[
<# if (!isStep) { #>
<div class="content tabs-content-item" id="tab-acti" data-entity="Acti">
<%Macro('WkldTabContentDetail', detail='Acti', $addlabel$='Add Link to Action')%>
</div>
<# } else { #>
<div class="content tabs-content-item" id="tab-acti" data-entity="Acti">
<%Macro('WkldTabContentDetailStep', detail='Acti', $addlabel$='Add Link to Action')%>
</div>
<# } #>
]}

WkldTabContentCase {[
<# if (!isStep) { #>
<div class="content tabs-content-item" id="tab-case" data-entity="Case">
<%Macro('WkldTabContentDetail', detail='Case', $addlabel$='Add Link to Incident')%>
</div>
<# } else { #>
<div class="content tabs-content-item" id="tab-case" data-entity="Case">
<%Macro('WkldTabContentDetailStep', detail='Case', $addlabel$='Add Link to Incident')%>
</div>
<# } #>
]}

WkldTabContentDocu {[
<# if (!isStep) { #>
<div class="content tabs-content-item" id="tab-docu" data-entity="Docu">
<%Macro('WkldTabContentDetail', detail='Docu', $addlabel$='Add Link to Document')%>
</div>
<# } else { #>
<div class="content tabs-content-item" id="tab-docu" data-entity="Docu">
<%Macro('WkldTabContentDetailStep', detail='Docu', $addlabel$='Add Link to Document')%>
</div>
<# } #>
]}

WkldTabContentMail {[
<# if (!isStep) { #>
<div class="content tabs-content-item" id="tab-mail" data-entity="Mail">
<%Macro('WkldTabContentDetail', detail='Mail', $addlabel$='Add Link to Mail')%>
</div>
<# } else { #>
<div class="content tabs-content-item" id="tab-mail" data-entity="Mail">
<%Macro('WkldTabContentDetailStep', detail='Mail', $addlabel$='Add Link to Mail')%>
</div>
<# } #>
]}

WkldTabContentOppo {[
<# if (!isStep) { #>
<div class="content tabs-content-item" id="tab-oppo" data-entity="Oppo">
<%Macro('WkldTabContentDetail', detail='Oppo', $addlabel$='Add Link to Opportunity')%>
</div>
<# } else { #>
<div class="content tabs-content-item" id="tab-oppo" data-entity="Oppo">
<%Macro('WkldTabContentDetailStep', detail='Oppo', $addlabel$='Add Link to Opportunity')%>
</div>
<# } #>
]}

WkldTabContentProd {[
<# if (!isStep) { #>
<div class="content tabs-content-item" id="tab-prod" data-entity="Prod">
<%Macro('WkldTabContentDetail', detail='Prod', $addlabel$='Add Link to Product')%>
</div>
<# } else { #>
<div class="content tabs-content-item" id="tab-prod" data-entity="Prod">
<%Macro('WkldTabContentDetailStep', detail='Prod', $addlabel$='Add Link to Product')%>
</div>
<# } #>
]}

WkldTabContentDetailStep {[
<div class="row">
<div class="small-2 medium-1 columns">
<button type="button" class="icon i-add" title="<%GetLabel('$addlabel$', context=ATTR)%>" data-msg="addLink;WrkStep;<#=@ data.key #>;$detail$"></button>
</div>
<div class="small-12 medium-11 columns">
<h3 class="section-title"><%GetLabel('$detail$s', context=TEXT)%></h3>
</div>
</div>
<div class="row">
<div class="small-12 columns wkld-detail-grid"></div>
</div>
]}

So I remove the if clause into the header and contents to remove the restriction on steps. And I added a macro called depending on if it's step or not. If yes the addling is done on WrkStep or if not on WrkStag.
I have missed something to finish the job.

Commit doesn't work on detail between custom entity and docu

Thu, 16 May 2019 13:51:36 +0000

Hello,

I have created a new entity named PAIEMENTS. I have added custom fields in the relation PAIE_DOCU.

As function AfterCommitOppoProd(oppoProdCxt, Inserted) works, I thought that « AfterCommitPaieDocu would work..... But, the folowing Commit operation doesn't work:

function AfterCommitPaieDocu(PaieDocuCxt, Inserted) {
var PaieDocuDS = Database.GetMasterDataset(PaieDocuCxt, 0);
var PaieKey = PaieDocuDS.FieldByName('K_PAIEMENT').AsFloat;
var DocuKey = PaieDocuDS.FieldByName('K_DOCUMENT').AsFloat;
var APayer = PaieDocuDS.FieldByName('F_A_PAYER').AsFloat;
var Paye = PaieDocuDS.FieldByName('F_PAYE').AsFloat;
var Ecart = PaieDocuDS.FieldByName('F_ECART').AsFloat;
var TotalPaye = Paye + Ecart;
PaieDocuDS.FieldByName('F_ENCAISSEMENT_VALIDE').AsInteger = 1;
Efficy.DisableWorkflow = true;
Efficy.CommitChanges(PaieDocuCxt, false);
Efficy.DisableWorkflow = false;
}

Do you know the reason?

The following command works:

function OnInsertDetailPaieDocu(EditHandle, Detail, DetailKey)

Thank you
Dimitri

Link Timesheet table to another table than project

Thu, 09 May 2019 19:53:42 +0000

Hello,

We did a customisation on the timesheet a few month ago that allow user to timesheet on opportunity or project.

The customisation work fine, the customer is happy, voilà.

BUT

Now, he want to "analyse" the data and make selections with them. Without native SQL, he cannot make a link between the table "timesheet" and "opportunities", by default.

I found the function tag <%SelectJoinTable()%> in dialog/Tables.htm. How can I change things in sys_relations and sys_relentities to have the possibility to link opportunities to Timesheet ?

Regards,

Loïc

Questions about system tables (adding relations, ...)

Wed, 10 Apr 2019 13:26:29 +0000

Hi,

I need to add ActiRelations in EditRelationsList.Oppo and I know that I have some SQL statements to execute in SQL Server. I'm trying to understand how the system tables work
Can you tell me if I am right or explain to myself:

SYSTABLES: Contains all existing tables in SQL Server. Efficy Designer uses it when the DB is "upgraded" (create/drop table)
SYSFIELDS: contains all the fields of each table (and virtual fields). Efficy Designer uses it when the database is "upgraded"
SYSRELATIONS: Efficy uses this to join different tables (and specify whether there is a join table)
SYSQUERIES: Efficy uses it to generate queries for obtaining data in Consult
SYSTABLEVIEWS: Efficy uses it to generate queries for obtaining data in Edit
SYSENTITYVIEWS: Contains collections of TABLESVIEWS to know which data to enter in which view
SYS_RELENTITIES: *I do not understand ??*

Sorry if I did not speak clearly but it's a little vague for me

I'm asking because I need to add ** ActiRelations ** to ** EditRelationsList.Oppo **.
I found a sample script that adds the OBJVPROF relationship with SQL statements. I'm trying to create my script from them.
But it contains the following SQL statement:
insert in SYSENTITYVIEWS (NAME, ISCUSTOM, TABLEVIEWS) values ('ObjvProf', 1, 'ObjvProf')

I looked for the relation Acti-Mail in this one and I can not find any entry ActiMail or MailActi

For the moment, my script looks like:

-- add Actions in OppoEdit
Update SYS_ENTITYVIEWS set ISCUSTOM=1, TABLEVIEWS=(SELECT TABLEVIEWS FROM SYS_ENTITYVIEWS WHERE NAME = 'OppoEdit') + ';Oppo_Acti=Acti' where NAME='OppoEdit' 


-- Get Acti data from OppoEdit
insert into  SYS_TABLEVIEWS (NAME, K_TABLE, ISCUSTOM, SELECTFROM, SELECTFIELDS, SELECTJOIN, SELECTORDERBY) 
values ('Oppo_Acti', @K_TABLE, 1, 'ACTI_OPPO ACTI_OPPO, ACTIONS ACTIONS', 'ACTI_OPPO.*, ACTIONS.SUBJECT, ACTIONS.D_BEGIN, ACTIONS.DONE', 'ACTI_OPPO.K_ACTION = ACTIONS.K_ACTION', 'ACTIONS.D_BEGIN DESC, ACTIONS.SUBJECT');

[Solution] Create and use a custom relation form for a K_RELATION between two Entities where there where no K_RELATION

Tue, 19 Feb 2019 19:32:31 +0000

Hello Efficy Team,

Because I would like that the Overflow become the source of knowledge for all our daily customisation, I took some time to put in a post a "tricky" customisation. This kind of demands are often asked by customer and we don't always respond to it the right way.

Create a custom relation form between Project and Contacts, using a K_RELATION

First step : add a KRELATION in PPROJCONT

For the context: Efficy is used to manage the leasing of products. Each product can be lease to the same person at different moment. There is always one contact for a single period, but the same contact could lease the same product (or collection of product) multiple time. This is why we use project and we need a K_RELATION.

Adding the KRELATION is quite simple. Just add the field "KRELATION" in the sysfields with DbEditor (with almost the same parameters as the KPROJECT and the K_CONTACT).

Then make an apply structure.

Second (very easy) step : creating the form in the designer

This is the easiest part. Use the designer to create a new form on the table "PROJ_CONT". Add the field that you've created.

Don't forget to write the K_FORM somewhere, this will be useful for the next step.

Add the "modify relation" button and show the form

2 macros need to be modified :

MacroConsultCustom

DetailMenu.Proj.Cont {[<%GetPopupMenu(id="detail-menu", class="has-icons small", ulargs='data-channel="detailmenu"', count="4",
     text1="Edit #DETAIL", image1="i-edit",
     message1="edit;{dropdownKey};#DETAIL",
     text2="Edit Relation", image2="i-link", onlinehelp2="e110_linkitems",
     message2=`editRelation;#ENTITY;#KEY;#DETAIL;{dropdownKey}`,
     text3="Delete Relation", image3="i-delete", onlinehelp3="e110_linkitems",
     message3="deleteRelation;#ENTITY;#KEY;#DETAIL;{dropdownKey}",
     text4="Add Call Back Task", image4="i-callback",  onlinehelp4="e110_createcallbacktasks",
     message4="addCallBack;#ENTITY;#KEY;;{dropdownKey}" 
)%>]}

Then you use the K_FORM of your new "custom Project - Contact"

MacroRelationCustom

RelationSectionsForm.Proj.Cont {[2]}

Editing the "good" relation

If you tested so far, you should see that you can "edit the relation" and your form is showing. But unfortunately, it does not show you current relation. Because we didn't specified witch relation need to be updated.

We first need to retrieve the KRELATION. For that, we'll duplicate the "KMASTER=0;KDETAIL=11" and we'll create a new "KMASTER=20;K_DETAIL=11"

We just add the K_RELATION on the column "by default" retrieved :

Then we'll overload the default "consult queries" for the relation "PROJ_CONT" :

MacroConsultCustom :

ConsultQueries.Proj.Cont {[
<%RunQuery(id="MainComp", SQL="select C.K_COMPANY, C.NAME from <#table name='PROJ_COMP'> PC, <#table name='COMPANIES'> C
    where C.K_COMPANY = PC.K_COMPANY and PC.K_PROJECT=:param1 and PC.MAIN=1", param1="#K", store="1")%>
<%RunQuery(id="MainCont", SQL="select C.K_CONTACT, C.NAME, C.MIDDLENAME, C.FIRSTNAME from <#table name='PROJ_CONT'> PC, <#table name='CONTACTS'> C
    where C.K_CONTACT = PC.K_CONTACT and PC.K_PROJECT=:param1 and PC.MAIN=1", param1="#K", store="2")%>

<%RunQuery(id="ListCont", MASTER="20", DETAIL="11", param1="%%GetKey()", mainquery="true")%> ]}

We also need to change the "{dropdownKey}" argument passed by our detailMenu (edited before). Efficy know the relation to edit by following this rule : "detailKey_relationKey". To do this, we'll overload the "MENU" definition, with this new rule :

MacroConsultCustom :

DetailGridColumns.Proj.Cont     {[MENU{RELATIONMENU},NAME,MIDDLENAME,FIRSTNAME{NAME},PHONE1{PHONE},PHONE2{PHONE},EMAIL1{EMAIL}]}

GridColumnCustom : 

th.RELATIONMENU {[<th class="icon-cell hide-for-print"> </th>]}
td.RELATIONMENU {[<td class="menu icon-cell hide-for-print"><span class="dropdown no-pip i-menu small" hello data-dropdown="detail-menu" data-args="<#F=K_CONTACT;context=ATTR>_<#F=K_RELATION;context=ATTR>"></span></td>]}

Then, ... it is done ! You'll be able to Edit the relation between project and contact, starting from the project. In my specific case it wasn't asked to do it starting from the contact itself but it wouldn't be hard to modify.

I hope it help you in the future,

Loïc

New Etity Relation : error Unknow EntityView ""

Mon, 07 Jan 2019 17:22:18 +0000

Hi,

I have a custom entity 'Missions', this entity use the PRODUCTS table too
FAMILY = 1 ==> Missions
FAMILY <> 1 ==> Products

My problem : When I want to add / delete a relation between a Mission and an other entity I have this error:

It works if I customize CreateRelation(), EditRelation(), DeleteLink() in Custom.js to replace 'Miss' by 'Prod' like this :

function DeleteLink(Bookmark, Entity, Key, Detail, DetailKey, ItemName, NoConfirm) {
    if (! NoConfirm) {
        var Msg = sRelDelConfirm
        if (ItemName) Msg = sRelDelConfirmName + ItemName + "' ?"
        if (! confirm(Msg)) return
    }

    if(Entity=='Miss') Entity='Prod' // FORCE MISSIONS TO PRODUCTS
    var URL = "deletelink?bookmark=" + Bookmark + "&entity=" + Entity + "&key=" + Key + "&detail=" + Detail + "&detailkey=" + DetailKey
    LocationSet(window, URL, true)
}

How to indicate to Efficy which EntityView use ?

Systems table for Missions :
SYS_ENTITIES

SYS_ENTITYVIEWS

avoid relation cont-comp modification

Tue, 10 Jul 2018 12:32:19 +0000

Hi,

I try to avoid the modification of a main relation using workflow and I get troubles:
With the code below when I try to modify or delete relation by edit relation on contact THIS WORK
but when I edit contact and change/delete on the right side the company link nothing is trigger and the link is change ???

How can I avoid the fact that the relation can be change on edit contact ?

Best regards.

here is my code:

function BeforeCommitContComp(EditHandle, Inserted) {
    log("beforeCommitContComp");
    var 
        ContCompDataSet = EfficyAPI.GetMasterDataSet(EditHandle, 0),
        ContKey = ContCompDataSet.FieldByName('K_CONTACT').AsFloat,
        ContMain = ContCompDataSet.FieldByName('MAIN').AsString;
    if(IsMainComp(ContKey) && ContMain == '0') {
        log("Vous ne pouvez pas changer la relation entre ce contact et une société mère ! k-contact=" + ContKey);
        throw new Error("You can't change relation between this contact and main company!");
    }
}

function OnBeforeDeleteContComp(Key, DetailKey) {
    log("OnBeforeDeleteContComp");
    if(IsMainComp(Key)) {
        log("Vous ne pouvez pas effacer le lien avec une société mère ! k_contact=" + Key);
        throw new Error("You can't delete relation with a main company!");
    }
}

Error on editing cont_comp relation

Tue, 03 Jul 2018 15:59:11 +0000

Hello,

We got a strange problem on the crm when editing a cont_comp relation with a custom fields added. When on a contact consult screen tab company if we try to modify relation everything is okay. But for the same contact in edit form screen when we want to modify the company relation an error occur (see screenshot). We try with no custom and we got the same error, so we know that came from database but we don't know where to fixe it.

How to insert a project and link it to a company

Fri, 25 May 2018 13:31:18 +0000

Hi everyone.

Im working on a method with the C# proxy for add 377 projects with the same Name (Reporting)

and link it to a company with the efficyKey.

here is my code : 

 try
        {
            List<Company> Companies = GetAllCompanies();
            Companies = Companies.Where(a => a.TypeRelation == CompRelationType.Participee || Convert.ToInt32(a.TypeRelation) == 9).Select(a => a).ToList();

            TContextHandle EditContext;

            foreach (var Iterator in Companies)
            {
                EditContext = Proxy.OpenEditContext("PROJ", 0);

                Hashtable Fields = new Hashtable();
                Fields.Add("NAME", "Reporting");

                Proxy.UpdateFields(EditContext, Fields);

                TContextHandle EditDocuProd = Proxy.OpenEditContextRelation("PROJ", EditContext.Key, "COMP", Iterator.EfficyKey, -1);
                Proxy.CloseContext(EditDocuProd);
            }
        }
         catch(Exception E)
        {
            DisposeProxy();
            Helper.LogHelper.LogMessage(Helper.LogHelper.MessageType.Error, "Error EfficyDataLayer.AddDossierForSoc()");
            Helper.LogHelper.LogExceptionMessage(E);
        }

I got an error after the CloseContext because the project is not link to any company.

Do u have the right method to do that ?

Thanks.

Vessiere Thomas.

Ancestors and descendants hierarchy in a relation table (SQL Server)

Wed, 17 Jan 2018 11:07:46 +0000

-- Get all descendant products given a parent product key
DECLARE @parentProductKey float = 200539; 
WITH PROD_HIERARCHY
AS
(
       SELECT DISTINCT
             PP1.K_PRODUCT K_PRODUCT_PARENT,
             PP1.K_PRODUCT2 K_PRODUCT_DESCENDANT
       FROM PROD_PROD PP1
             LEFT JOIN PROD_PROD PP2 ON PP1.K_PRODUCT2 = PP2.K_PRODUCT
       WHERE PP1.K_PRODUCT = @parentProductKey
       UNION ALL
       SELECT
             H.K_PRODUCT_PARENT,
             PP.K_PRODUCT2
       FROM PROD_HIERARCHY H
             INNER JOIN PROD_PROD PP ON H.K_PRODUCT_DESCENDANT = PP.K_PRODUCT
)
SELECT * FROM PROD_HIERARCHY

-- Get all ancestor products given a descendant product key
DECLARE @descendantProductKey float = 202099; 
WITH PROD_HIERARCHY AS
(
    SELECT  K_PRODUCT2 K_PRODUCT_DESCENDANT, 
            K_PRODUCT K_PRODUCT_PARENT 
    FROM    PROD_PROD
       WHERE K_PRODUCT2 = @descendantProductKey
    UNION ALL
    SELECT  PP.K_PRODUCT2, 
            PP.K_PRODUCT 
    FROM    PROD_PROD PP
            INNER JOIN PROD_HIERARCHY H ON H.K_PRODUCT_PARENT = PP.K_PRODUCT2
)
SELECT * FROM PROD_HIERARCHY

Filed Modified on relation prod_oppo

Wed, 07 Jun 2017 10:49:39 +0000

Hello,

Is there a way to use FiledModified method to know if field like PRICE has been changed on relation prod_oppo?

Thank you in advance for your help.

Best Regards.

Efficy 2014 - Where is the little pencil on Docu_Prod ?

Tue, 17 Feb 2015 21:00:18 +0000

Dear all,

Before in Efficy 2012 when we add a panel in a relation table (from conficy) a little pencil displayed automatically in Efficy and when the user clicked on it, all the fields in the pannel was editable. (for instance in the Documents on the product lines)

For Efficy 2014, the products line are also available in Opportunities, but I could not find this features.

Do we still have such feature in Efficy 2014 ?

if so, how can I display it ?

Best Regards,
Stéphane RONCIN