No RelationKey (optional) parameter for OnInsertDetailXxxxYyyy event

Wed, 31 Jul 2019 09:45:55 +0000

When scripting the OnInsertDetail event, we're not provided the (optional) relationKey parameter.
Consequently, it becomes a nightmare when you want to edit the newly inserted detail relation : I hoped the new detail would be the last one in the detailDataset but its position is not reliable.

This is to my mind a decent change request.

I've tried set the SELECTORDERBY clause of the SYSTABLEVIEWS to XXXXYYYY.D_CHANGE, but this isn't reliable.
=> I use a custom fied to know if a detail has been processed or not by my workflow :-(

Any comment is welcome.

[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

How to determine K_RELATION in DOCU_PROD using a direct database-update

Fri, 11 Jan 2019 20:39:27 +0000

I'm trying to insert rows in the table DOCU_PROD using an external program. So I'm not able to use Efficy-functions.

All columns are quite logical, but I'm not sure how to determine the content of K_RELATION? Can I just define a random value? Or is it (as the name of the column suggests) a relation to another table? As far as I have seen the values do not need to be unique.

Edit: I tried to set KRELATION = 0. But when trying to edit the document afterwards it results in the following error: Vind detail met sleutel "97" en relatie "612593356" niet terug
so somehow there must be a logical way to deterime KRELATION. Does someone know?

OnBeforeDeleteProdProj(key, detailKey, krelation) called with undefined krelation...

Mon, 18 Apr 2016 11:44:48 +0000

Hi,
I added a KRELATION column to the table "PRODPROJ".

It run well everywhere, except the OnBeforeDeleteProdProj(key, detailKey, krelation) function, which is call with an undefined value for the "krelation" parameter...

Where is the problem ?
Thanks
Didier

Efficy Overflow Q&A - Recent questions tagged k_relation