You are here:
Bindings
Use the Declarations macro path to bind dynamic data. You can use optional attributes in macros to define the typical bindings for the repetitive variables in the each and correlation nodes.

Use more general search terms.
Select fewer filters to broaden your search.
You are here:
Use the Declarations macro path to bind dynamic data. You can use optional attributes in macros to define the typical bindings for the repetitive variables in the each and correlation nodes.
| Available in Lightning Experience in Enterprise and Unlimited Editions that have Consumer Goods Cloud enabled. |
Declarations replaces the macro content with the value
in the referenced BusinessObject or ListObject. For example, {{Declarations::salesOrg.houseNumber}}. Initially, you are required to declare the
BO or the LO in the DataDeclaration attribute, later you
can use the variables associated with these objects to define the macros path. If the macros
path results in null or is unresolved, the macro is shown in the output document for
debugging.
In this example, the macros path is defined for extracting the address data. The sales org
object is declared with the LuSalesOrg type in the
DataDeclaration attribute. When the path {{Declarations::salesOrg.houseNumber}} is run, the print engine performs the data
lookup for the houseNumber variable, extracts the
associated value, and shows the value in the document.
<!-- left out details for brevity -->
<Declarations>
<DataDeclaration name="order" type="BoOrder" />
<DataDeclaration name="salesOrg" type="LuSalesOrg" />
</Declarations>
<ReportLayout pageMargins="[40,40,40,40]">
<table name="ManufacturerTable" dontBreakRows="false" tableLayout="noBorders">
<tbody>
<tr>
<td alignment="right">{{Labels::AddressId; defaultLabel=Address:}}</td>
<td>{{Declarations::salesOrg.houseNumber}} {{Declarations::salesOrg.street}} {{Declarations::salesOrg.zipCode}} {{Declarations::salesOrg.city}}</td>
</tr>
</tbody>
</table>
</ReportLayout>

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.