Efficy Overflow Q&A - Recent questions tagged enterprise

Does Enterprise <> Apsis connector accept virtual fields on field mapping ?

Tue, 01 Jul 2025 13:41:14 +0000

Hello,

Did someone used a virtual (V_ with usage P) field during a mapping between Enterprise <> Apsis ?
I was told that virtual fields are supported by Enterprise <> Apsis connector. It is possible to select the field during the mapping (Apsis interface). But when running the full sync I am getting the error that V_ fields is invalid column name which is normal in Enterprise as it's a virtual field.

To get the contacts based on mapped fields in Apsis, Apsis calls an Enterprise node/api end point serverjs\api\node\marketing\apsis\contacts.js which calls a function from serverjs\marketing\apsis.js > contacts that runs a query using the provided list of fields from a payload.

Internal replies from @Kristof Pauwels:

The consult, list and search API do not support virtual fields, they
are always excluded from the result. That's not wrong on itself, it
guarantees the best performance. Only when running a query, virtual
fields can be included. So it will depend on what operation the Apsis integration uses. There are dedicated Apsis system queries and ServerJs node endpoints..
You can also decide to override the contacts method with a custom
version. Try using the <#Field> tag and see if its replaced by the
SQL expression, else you have to hardcode the SQL expression and
alias it as V_MYCOLUMN.

How to make appear a filter on same fields for different entities in query builder ?

Tue, 27 May 2025 07:40:28 +0000

Hello,

Imagine you have a query that shows list of document and the contacts that are linked to it.

The selection fields will be DOCUMENTS.NAME, CONTACTS.NAME, CONTACTS.FIRSTNAME, etc..

When running the query I've get the grid with the results. On the header of DOCUMENTS.NAME I have a filter that allows to search/filter by document name.

When looking into CONTACTS.NAME header the filter is not present.

From what I understand the same field naming NAME causes the issue. But when I set an alias on one of them I loose the filter too.

How could I manage to show the filter on both NAME fields ?
Should I name (alias) a field and use the alias to create a grid definition to make include the filter ?

Update:

Finally with custom definition of an ALIAS it works.

In GridColumnsCustom.txt:

th.ContactName {[<th class="text-center nowrap"><#H=$FIELD$;sort=true;hfilter=true></th>]}

The main point is to have the propriety hfilter=true.

To make it more generic alias ENTITYNAME.
GridColumnsCustom.txt:

th.ENTITYNAME {[<th class="text-center nowrap"><#H=$FIELD$;sort=true;hfilter=true;Text=$ENTITY$Name></th>]}

And the $ENTITY$Name depending on entity will be ContName, CompName, etc... can be translated in CustomLabels.txt.

Did You Know? PDF Hack for Nitro Signature Tags!

Tue, 13 May 2025 16:59:23 +0000

Did You Know? PDF Hack for Nitro Signature Tags!

Game-changing discovery: You can add Nitro signature tags directly to PDF files without converting from Word!

The Challenge

One of our clients, recently shared their frustration with our standard process:

They were told they needed to create documents in Word
Add Nitro tags like in Word
Convert to PDF
Only then send for signatures through our module

This workflow was particularly cumbersome for their team who primarily works with PDF files.

The Solution We Discovered
During a client call, we tested a simple but effective workaround:

Open the PDF directly in Adobe Acrobat Reader
Add a text element containing the Nitro tag (e.g., )
Change the text color to match the background (making it invisible)
Save the file
Upload to Enterprise document and create a signature request

The Result

✅ Success! Nitro correctly identified the hidden tags and replaced them with signatures

✅ The client received properly signed documents

✅ No Word-to-PDF conversion needed!

Client Feedback

"Next time when pitching to clients, don't forget to tell them they can use PDF directly to include tags. This could make a big difference and avoid misguiding cases like we had."

This small change can significantly improve workflow efficiency for clients who primarily work with PDFs!

How to show only the records directly linked to the connected user in list view (USERSELECTION query tag)?

Wed, 09 Apr 2025 14:02:26 +0000

@Stéphane Roncin pointed out that , since the Enterprise 2021 and + , the Oppo list view don't show the records of groups that are linked to the record and the connected user is part of (linked to the group). It only shows the records that are directly linked to the user. Which wasn't the case for version under 2021.

The difference is in the the SYSQUERIES: KMASTER(22), K_DETAIL(0).
<#USERSELECTION usertable="OPPO_USER" key="K_OPPORTUNITY" isactiveparam="true" directlink="true"> U1 the argument directlink="true".

directlink - Optional argument, if not empty, consider only items directly linked to the users, do no consider groups (see: https://help.efficy.io/edn/querytags#userselection) . In case if you want the behavior from previous versions just remove the argument directlink.

Now. If you want to have the same behavior as in Oppo for other Entities list view you need to change the SYS_QUERIES list of your entity and use USERSELECTION.

Ex.: Companies List (SYSQUERIES: KMASTER(10), K_DETAIL(0))

Standard version:

[Select]
COMPANIES.K_COMPANY
COMPANIES.NAME
COMPANIES.BUILDING
COMPANIES.CITY
COMPANIES.COUNTRY
COMPANIES.PHONE1
COMPANIES.EMAIL1
COMPANIES.WEB1
COMPANIES.OPENED
COMPANIES.LONGITUDE
COMPANIES.LATITUDE
COMPANIES.TAGS
COMPANIES.D_CREATE
COMPANIES.D_CHANGE
COMPANIES.MEMO
COMPANIES.MEMOFORMATTED

[From]
COMPANIES

[Where]
COMPANIES.OPENED = 0
<#USERLINK table="COMPANIES" usertable="COMP_USER" key="K_COMPANY" isactiveparam="true">

[Orderby]
COMPANIES.NAME

[Columns]
MENU,NAME,CITY,R_COUNTRY,PHONE1{PHONE},EMAIL1{EMAIL},TAGS

Customized version:

[Select]
COMPANIES.K_COMPANY
COMPANIES.NAME
COMPANIES.BUILDING
COMPANIES.CITY
COMPANIES.COUNTRY
COMPANIES.PHONE1
COMPANIES.EMAIL1
COMPANIES.WEB1
COMPANIES.OPENED
COMPANIES.LONGITUDE
COMPANIES.LATITUDE
COMPANIES.TAGS
COMPANIES.D_CREATE
COMPANIES.D_CHANGE
COMPANIES.MEMO
COMPANIES.MEMOFORMATTED

[From]
COMPANIES
<#USERSELECTION usertable="COMP_USER" key="K_COMPANY" isactiveparam="true" directlink="true"> U1

[Where]
COMPANIES.OPENED = 0
<U1.<#FIELD name="K_COMPANY" fortable="COMP_USER"> = COMPANIES.K_COMPANY>

[Orderby]
COMPANIES.NAME

[Columns]
MENU,NAME,CITY,R_COUNTRY,PHONE1{PHONE},EMAIL1{EMAIL},TAGS

It is not mentioned in "Efficy Query Tag" documentation but you have to update SYS_SETTINGS too.
Designer > SYS_SETTINGS > Efficy > entityListsWithTagUserSelection.

The entityListsWithTagUserSelection takes into account the keys of entities separated by semicolon ";". Ex.: "entityListsWithTagUserSelection": "10;22",. (22 is Oppo per default)
If you don't provide the entity in SYS_SETTINGS the USERSELECTION will not behave as intended.

Many thanks to Stephane Roncin for pointing it out and for explaining.