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.

Efficy Overflow Q&A - Recent questions tagged apsis

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