Efficy Overflow Q&A - Recent questions tagged create-relation

Create a conditionnal DetailMenu

Sun, 19 May 2019 12:05:15 +0000

Hello,

We would like to customise Efficy in order to have a DetailMenu, with a condition in it.

The macro is the following one :

DetailMenu..Docu {[<%GetPopupMenu(id="detail-menu", class="has-icons small", ulargs='data-channel="detailmenu"', count="6",
text1="Edit #DETAIL", image1="i-edit",
message1="edit;{dropdownKey};#DETAIL",
text2="Delete #DETAIL", image2="i-delete",
message2="deleteItem;#DETAIL;{dropdownKey}",
text3="Edit Relation", image3="i-link", onlinehelp3="e110_linkitems",
message3=`%%IfCategories(then="editRelation;#ENTITY;#KEY;#DETAIL;{dropdownKey}")`,
text4="Duplicate #DETAIL", image4="i-Dupl", onlinehelp4="e110_duplicateitems",
message4="duplicate;#DETAIL;{dropdownKey}",
text5="Mark as Handled", image5="i-done",
message5="markDocumentHandled;{dropdownKey};0",
text6="Convert to Opportunity", image6="i-Oppo", rights6="Oppo", onlinehelp6="e110_convertitems2salesopp",
message6="convertToEntity;Oppo;#DETAIL;{dropdownKey};Comp\\;Cont\\;Proj\\;Prod;true;NAME"
)%>]}

What I would like to do is detect the reference or a field value of the document to propose other options.
But the dev on this cannot make it work.

He tried this, but it does not seems to work "efficiently" (it always show the option, whatever the reference)

DetailMenu..Docu {[
<%GetPopupMenu(
id="detail-menu", class="has-icons small", ulargs='data-channel="detailmenu"', count="7",
text1="Edit #DETAIL", image1="i-edit",
message1="edit;{dropdownKey};#DETAIL",
text2="Delete #DETAIL", image2="i-delete",
message2="deleteItem;#DETAIL;{dropdownKey}",
text3="Edit Relation", image3="i-link", onlinehelp3="e110_linkitems",
message3=`%%IfCategories(then="editRelation;#ENTITY;#KEY;#DETAIL;{dropdownKey}")`,
text4="Duplicate #DETAIL", image4="i-Dupl", onlinehelp4="e110_duplicateitems",
message4="duplicate;#DETAIL;{dropdownKey}",
text5="Mark as Handled", image5="i-done",
message5="markDocumentHandled;{dropdownKey};0",
text6="Convert to Opportunity", image6="i-Oppo", rights6="Oppo", onlinehelp6="e110_convertitems2salesopp",
message6="convertToEntity;Oppo;#DETAIL;{dropdownKey};Comp\\;Cont\\;Proj\\;Prod;true;NAME",
`%%OnField("MakeNCG", query="select CASE WHEN /*doc.REFERENCE LIKE 'DRAFT-%' OR */doc.REFERENCE LIKE 'NC-%' OR doc.id_kleos IS NOT NULL OR doc.F_INVOICE_STATUS < 4 THEN 0 ELSE 1 END AS MakeNCG from DOCUMENTS doc where doc.K_DOCUMENT = {dropdownKey}", value=1, then="text7=`Make NC Globalazzz`, image7=`i-edit`, message7=`NCGlobal;{dropdownKey}`", else="text7=`Make NC non`, image7=`i-edit`, message7=`NCGlobal;{dropdownKey}`")`
)%>]}

I suppose there is a way to :

Make this "clean"
Avoid a SQL query

Regards,

Loïc

[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

Trouble ceating a relation between Cont and new entity

Wed, 12 Dec 2018 10:00:16 +0000

Hi,

I create a new entity named Trai (key 50) and with a servercript I try to create a relation between this entity and a contact. I got an error when I try to link this contact by script but work if I use the right side of the edit form contacts (add link to a contact). To debug I run this script from the scheduler and got this message

Error: WKFL-2142 Error while executing script "bentest" at line 1020 char 4. (File "C:\inetpub\wwwroot\11.0\customs\xxx\serverscripts\NLservertest.js" line 25)
Message: "Incorrect Detail for Edit Context"

function bentest() {
    var editHandle = Efficy.openEditContext(ntCont, 67067, false);
        try{
            var ds = Efficy.getMasterDataSet(editHandle, 0);
            ds.edit();
            Efficy.insertDetail2(editHandle, 50, 64, false);
            Efficy.commitChanges(editHandle, true);
        } finally {
            Efficy.closeContext(editHandle);
        }   
}

line 25 is the insertDetail2 line.

Best method to override search

Mon, 17 Sep 2018 10:25:55 +0000

Hi Guys,

I was wondering if there's a nice and clean way to override the result of the search page with a custom function?

What i need is the following:

Open the standard search window from a relational detailmenu with the normal search features of Efficy and the createrelation action (so you can also create a new relational record)
If you click on one of the search result records, a custom function needs to start.

Hopefully someone has a simple way to do it, instead of overriding all pages and macro's.

Kr,

Michael de Groot

CreateRelation on new Entity : how does this work ?

Thu, 12 Apr 2018 12:19:10 +0000

Dear All,

I am trying to search how the relation is created when you click on the + button in the consult grid of an entity. It bring the search window, but when you click on the Add new button in the search button ... then I am confused. Here is what I understand :

1- when I click on the + button in the consult, it open the search window with the parameter
"action=CreateRelation(1009%3BProp%3B1186)" ... which is used to add the key of the selected entity in this function if I click directly in the search result. Which is ok and I have my hand on it if I want.

2- if I click on the Add new button in the search button, the parameter is transfer to the Edit windows of the new Entity we want to create "action=CreateRelation(1009%3BProp%3B1186)"
But when I clicked on "OK" or "APPLY", the new entity is created and I don't know where Efficy has created the linked using the information in the action passed in the URL ...

The issue is that when we do that the new entity is becoming the parent of the entity where we click on the create relation button, but normally it should be the child.

And I don't know where this happened.

PS : I suspect that this is handled in the Efficy.dll ... but I would like a confirmation of it.

Best Regards,
Stéphane