Value Expression, Replication Document Elements

Macro	Description
`ACTION()`	Used with `TABLE!` BODs For an insert operation that fired the replication, this expression gets the value Add. For an update operation, this expression gets the value Change. Delete is currently undefined and substitutes to an empty string.
`PARMS( table.column )`	Resolves to the value of the specified table or column
`FPARMS`	Mimics the behavior of PARMS, but encloses the result in single quotes, for filters
`P(property)`	Specifies the value of an IDO property
`FP(property)`	Mimics the behavior of `P()`, but encloses the result in single quotes, for filters
`Pn`	Used for method parameters Method parameters are referenced by numerical order, rather than by a specific property name. For example, `P7` indicates the seventh method parameter.
`FPn`	Used for method parameters Mimics the behavior of `Pn`, but encloses the result in single quotes
`NIDID(property\|param\|literal)`	Resolves to the value of the NID with the location left blank To use this, specify a property name, an invoke parameter name, or a literal string with substitution keywords. The macro then retrieves the rest of the information required for the NID from the application.
`LNIDID(property\|param\|literal)`	Resolves to the value of the NID including the location or the "from" site Specify a property name, an invoke parameter name, or a literal string with substitution keywords. The macro then retrieves the rest of the information required for the NID from the application.
`TNIDID(property\|param\|literal)`	Mimics the behavior of the `NIDID` keyword, but does not include accounting entity or location in the return value Specify a property name, an invoke parameter name, or a literal string with substitution keywords. The macro then retrieves the rest of the information required for the NID from the application.
`BODNOUN()` or `BODVERB()`	Resolves to the value of the BOD noun and verb from the linked Replication Document Inbound Cross-References form or Replication Document Outbound Cross-Reference form On the Replication Document Elements form, the BODNOUN and BODVERB keywords are honored in these fields: Value Expression BOD Tag Name Attribute To employ the replication document as a template and resolve to a different outer XML element, which depends on the noun and verb combination selected on the cross reference form, use these keywords. For example, the Purchase Order Sync BOD must specify `SyncPurchaseOrder` as the outermost XML element name. The Purchase Order Process BOD must specify `ProcessPurchaseOrder` as the outermost XML element name. Instead of specifying this information, use `BODVERB()BODNOUN()` to specify the verb and noun in the PurchaseOrder replication document's BOD Tag Name field. This method allows you to use the same replication document for both verbs. Be careful not to include blanks when using these keywords for tag and attribute names, because blanks are not allowed in XML names.
`BODXML()`	Allows inbound BODs metadata to pass the entire XML to a method For example: `UPD(SaveCallSp(BODXML()))`
`FROMLOGICALID()`	Resolves to the value of `site.message_bus_logical_id` for the site that is the source of the original outbound message with an optional "`:ims`" suffix (as dictated by the setting in the site's intranet); and then appends the `parms.site` value for that site. Note that this produces a well-formed URI with a "`lid://`" prefix. For example: `lid://infor.mongoose.mongoose:ims/oh`
`FROMLOGICALIDLEGACY()`	Mimics the legacy behavior of the `FROMLOGICALID()` macro; however, it does not prepend the schema or the "`:ims`" suffix. The resultant value is produced by combining the `site.message_bus_logical_id` value with the site name. For example: `infor.mongoose.mongoose/oh`
`FROMLOGICALIDWITHOVERRIDE()`	Mimics the behavior of the site logical ID If there is a value for the process default property Outbound SUM Role LID Override, then the override value is used. If there is no value in the process default property and no override is specified, the value returns to the same value as FROMLOGICALID().
`BODCURDATETIME()`	Resolves to the current server-based date or time, formatted for BOD-enabled applications
`VARIATIONID()`	Resolves to a 64-bit integer value that is guaranteed to be unique
`TENANTID()`	Resolves to the Tenant ID value as set on the Sites form. the Sites/Entities form, or Intranets form.
`FROMSITEINTRANET()`	Mimics the behavior of `TENANTID`
`URIFROMSITEINTRANET()`	Formats the URI-encoded `FROMSITEINTRANET`, so that URI characters, such as "/" are escaped
`URITENANTID()`	Formats the URI-encoded `TENANTID`, so that URI characters, such as "/" are escaped
`CDATA()`	Wraps the entire element so that all XML tags are ignored using the XML CDATA construct The `CDATA()` specification must be at the beginning of the element. Otherwise, it is ignored. If `CDATA()` is found at the start of an element value, then the value will be made a CDATA section. For example: `CDATA()P(P3)`

ACTION()

Used with TABLE! BODs

For an insert operation that fired the replication, this expression gets the value Add.
For an update operation, this expression gets the value Change.

Delete is currently undefined and substitutes to an empty string.

PARMS( table.column )

Resolves to the value of the specified table or column

FPARMS

Mimics the behavior of PARMS, but encloses the result in single quotes, for filters

P(property)

Specifies the value of an IDO property

FP(property)

Mimics the behavior of P(), but encloses the result in single quotes, for filters

Pn

Used for method parameters

Method parameters are referenced by numerical order, rather than by a specific property name. For example, P7 indicates the seventh method parameter.

FPn

Used for method parameters

Mimics the behavior of Pn, but encloses the result in single quotes

NIDID(property|param|literal)

Resolves to the value of the NID with the location left blank

To use this, specify a property name, an invoke parameter name, or a literal string with substitution keywords. The macro then retrieves the rest of the information required for the NID from the application.

LNIDID(property|param|literal)

Resolves to the value of the NID including the location or the "from" site

Specify a property name, an invoke parameter name, or a literal string with substitution keywords. The macro then retrieves the rest of the information required for the NID from the application.

TNIDID(property|param|literal)

Mimics the behavior of the NIDID keyword, but does not include accounting entity or location in the return value

Specify a property name, an invoke parameter name, or a literal string with substitution keywords. The macro then retrieves the rest of the information required for the NID from the application.

BODNOUN() or BODVERB()

Resolves to the value of the BOD noun and verb from the linked Replication Document Inbound Cross-References form or Replication Document Outbound Cross-Reference form

On the Replication Document Elements form, the BODNOUN and BODVERB keywords are honored in these fields:

Value Expression
BOD Tag Name
Attribute

To employ the replication document as a template and resolve to a different outer XML element, which depends on the noun and verb combination selected on the cross reference form, use these keywords.

For example, the Purchase Order Sync BOD must specify SyncPurchaseOrder as the outermost XML element name. The Purchase Order Process BOD must specify ProcessPurchaseOrder as the outermost XML element name. Instead of specifying this information, use BODVERB()BODNOUN() to specify the verb and noun in the PurchaseOrder replication document's BOD Tag Name field. This method allows you to use the same replication document for both verbs.

Be careful not to include blanks when using these keywords for tag and attribute names, because blanks are not allowed in XML names.

BODXML()

Allows inbound BODs metadata to pass the entire XML to a method

For example: UPD(SaveCallSp(BODXML()))

FROMLOGICALID()

Resolves to the value of site.message_bus_logical_id for the site that is the source of the original outbound message with an optional ":ims" suffix (as dictated by the setting in the site's intranet); and then appends the parms.site value for that site. Note that this produces a well-formed URI with a "lid://" prefix.

For example: lid://infor.mongoose.mongoose:ims/oh

FROMLOGICALIDLEGACY()

Mimics the legacy behavior of the FROMLOGICALID() macro; however, it does not prepend the schema or the ":ims" suffix.

The resultant value is produced by combining the site.message_bus_logical_id value with the site name.

For example: infor.mongoose.mongoose/oh

FROMLOGICALIDWITHOVERRIDE()

Mimics the behavior of the site logical ID

If there is a value for the process default property Outbound SUM Role LID Override, then the override value is used. If there is no value in the process default property and no override is specified, the value returns to the same value as FROMLOGICALID().

BODCURDATETIME()

Resolves to the current server-based date or time, formatted for BOD-enabled applications

VARIATIONID()

Resolves to a 64-bit integer value that is guaranteed to be unique

TENANTID()

Resolves to the Tenant ID value as set on the Sites form. the Sites/Entities form, or Intranets form.

FROMSITEINTRANET()

Mimics the behavior of TENANTID

URIFROMSITEINTRANET()

Formats the URI-encoded FROMSITEINTRANET, so that URI characters, such as "/" are escaped

URITENANTID()

Formats the URI-encoded TENANTID, so that URI characters, such as "/" are escaped

CDATA()

Wraps the entire element so that all XML tags are ignored using the XML CDATA construct

The CDATA() specification must be at the beginning of the element. Otherwise, it is ignored. If CDATA() is found at the start of an element value, then the value will be made a CDATA section. For example: CDATA()P(P3)