CustomerAddress class properties map to Limio address fields as follows:
CustomerAddress property | Limio address field | |
1 |
FirstName
|
firstName |
2 | LastName | lastName |
3 | CompanyName | company |
4 | MailingStreetName | streetName |
5 | MailingBuildingNumber | buildingNumber |
6 | MailingStreet | address1, address2 (split by new line) |
7 | MailingCity | city |
8 | MailingCountry | country |
9 | MailingState | state |
10 | MailingPostalCode | postalCode |
All of the properties above are of type String, also they are global and invocable, which means you can access them and assign them values from within the SF flow context. You can find this class definition in the Apex Classes in Setup as well.
What is the difference between MailingStreet and MailingStreetName ?
LFS version 12.10 introduced two new properties: MailingStreetName and MailingBuldingNumber.
As you see from the table above, MailingStreet maps to an address1, address2 (separated on the new line), it usually contains street name and building number combined.
If you need to map street name and building number into two standalone fields use MailingStreetName for streetName and MailingBuldingNumber for buildingNumber instead.
Other global invocable properties
There are two more global invocable properties in the class related to the Address Book, learn more here: Flow Customisation: Add additional addresses to the address book
- label - used to represent an address option in the Address Book dropdown
- id - required for all address book entries, needs to be specified before adding a new address to the Address Book
Comments
0 comments
Please sign in to leave a comment.