Injection parameters
Injection Parameters are the paths and fields that make up an injection for Smart link click, Smart link fetch, Smart rules, and Smart events. Valid Injections can contain parameters from the sources described on this page.
Intacct fields
Every Intacct object has an associated set of fields. The fields are listed below the object in the Customization Services Catalog (see Understand the Catalog). An Intacct field is described by the object ID, followed by a period, followed by the field ID:
OBJECT_ID.FIELD_ID
For instance, if you want your injection to reference the due date field for an invoice, use the catalog to look up the INVDOCUMENT object. Then find the ID for the due date field, which is WHENDUE and write the injection parameter:
INVDOCUMENT.WHENDUE
Custom fields
Injection parameters can also reference custom fields the same way they reference Intacct fields. Custom fields can be found in the Catalog under the object they extend.
Nexus fields
Objects are joined together in their nexus. Injections become more complex as steps increase between the extended object and the desired field. In cases where multiple steps occur, understanding the nexus becomes important. You can view the nexus of an object and the objects associated with it in the catalog. When viewing your selected object, scroll to Nexus (Related objects).
Let's say you extend the INV Document; you can still add Injections using any of the fields belonging to the objects listed in the INVDOCUMENT nexus. To write this path, start with the root object and add values from the object path column in the nexus. Finish with the field name from the last related object.
For example, if you extend the INV Document and want an Injection to go to the Primary URL of the Contact listed in the BILLTO field, write:
INVDOCUMENT.BILLTO.URL1
Or lets say you need an injection that goes to the country for the Contact listed in the BILLTO field. In this case, you would jump from the nexus for INVDOCUMENT to the nexus for CONTACT and use a field from the Object Path MAILADDRESS and related Object MAILADDRESS:
INVDOCUMENT.BILLTO.MAILADDRESS.COUNTRY
You might use this injection as part of a Smart rule that produces a warning for INV documents where the Bill-to address is outside a specified country.
Nexus custom fields
When a custom field is added to an object, it shares all the nexus relationships of that object. You can use a nexus relationship to write an injection for a custom field in a related object.
Universal objects
Standard and custom user fields in some objects can be included as injection parameters regardless of the object being extended. Objects that contain fields that can always be used as injection parameters include:
- CURRENTUSER
- COMPANY
- USERPROFILE
Universal values
You can always use the following Intacct injection parameters.
| Parameter | Description |
|---|---|
{!USERPROFILE.SESSIONID!}
|
session ID |
{!API_ENDPOINT!}
|
API endpoint for callbacks (use with session ID as a best practice) |
{!USERPROFILE.LOGIN!}
|
user ID |
{!USERPROFILE.NONSTANDARDPERIODS!}
|
custom accounting periods |
{!USERPROFILE.EMAIL!}
|
user email |
{!USERPROFILE.LOCATIONKEY!}
|
key (not ID) of the current entity, if user slides into it |
{!USERPROFILE.ISMULTIENTITY!}
|
if company is multi-entity |
{!USERPROFILE.CONTEXTLOCATION!}
|
returns ROOT if at the shared top level, or if slide-in, returns [LOCATIONKEY]--[LOCATIONNAME] of the entity. |