Overview
The Syspro integration provides a set of ready-made functions you can call when building mappings. They handle common lookups and conversions for Syspro, such as finding a customer by email address and pulling a description from a product's variants, so you do not have to write that logic yourself in a formula.
Where you can use these functions
These functions are available anywhere you write a formula for the Syspro integration:
Dynamic Formula mappings: where a destination field's value is produced by a formula rather than mapped directly from a source field.
Mapping collection filters: where a formula decides whether a record should be processed.
Error filters: a mapping collection's error filter, which sits alongside its collection filter. When the error filter's formula resolves to true, the transfer raises an error that is held in the Error Logs for review and is not retried automatically.
Translation collections: where a translation entry uses a formula as its source value.
How to use them
Call a function by name and pass the values it needs in parentheses, for example:
CustomerFromEmail(SourceEmail).Each function's signature shows its name, the parameters it accepts (with their types), and the type of value it returns. Use it as the reference for exactly how to call the function.
Function names and formula syntax are case-sensitive, so type each name exactly as shown. Whether the values a function matches are treated as case-sensitive varies by function, and is called out in the relevant parameter's description.
These functions are synchronous, so you call them directly (no
awaitis required).Each function runs at sync time, against the data in your connected Syspro account and your iPaaS.com subscription.
The functions are grouped below by the area of the integration they support.
Customers
CustomerFromEmail
What it does: Finds a Syspro customer by email address and returns that customer's number. If more than one customer has the address, the first match is used.
Signature: string CustomerFromEmail(string matchValue)
How to call it: CustomerFromEmail(matchValue)
Parameter | Type | Required | Default | Description |
|
| Yes | N/A | The iPaaS.com customer email address to match against Syspro customers. |
Returns: string. The Syspro customer number for the first customer with that email, or null if no customer matches.
Example: "myaddress@email.com" returns the Syspro customer number for the customer with that email.
When to use it: Use this when a mapping needs the Syspro customer number and you have only the customer's email address.
Products
VariantParent_LongDescriptionFromChild
What it does: Returns the long description to use for a variant parent product, taken from its first variant. If there are no variants, it returns the text Variant Parent.
Signature: string VariantParent_LongDescriptionFromChild(List<Product> variants)
How to call it: VariantParent_LongDescriptionFromChild(variants)
Parameter | Type | Required | Default | Description |
|
| Yes | N/A | The variant products of the parent. The first variant's long description is used. |
Returns: string. The long description from the first variant, or Variant Parent when the list is empty.
Example: A list of variants returns the long description of the first variant.
When to use it: Use this when a variant parent product needs a long description derived from its variants.
VariantParent_DescriptionFromChild
What it does: Returns the description to use for a variant parent product, taken from its first variant. If there are no variants, it returns the text Variant Parent.
Signature: string VariantParent_DescriptionFromChild(List<Product> variants)
How to call it: VariantParent_DescriptionFromChild(variants)
Parameter | Type | Required | Default | Description |
|
| Yes | N/A | The variant products of the parent. The first variant's description is used. |
Returns: string. The description from the first variant, or Variant Parent when the list is empty.
Example: A list of variants returns the description of the first variant.
When to use it: Use this when a variant parent product needs a description derived from its variants.