PLAT-DEV-210 practice question 6 of 25

A developer is configuring the API URL in an HTTP Action element within an Integration procedure. What is the merge code syntax for passing a Date node from an element named SetValues in the URL?

Full set: 103 questions
Answer options
A: x%SetValues.Date% Correct answer
B: (‘ Setvalues’] [ ‘Date’]
C: %SetValues Date
D: {(SetValues. Date)}
Correct Answer:
A. x%SetValues.Date%
Explanation

The correct syntax to reference a data node from a previous element within an Integration Procedure's URL is %ElementName:JSONPath%. In this scenario, the element is SetValues and the node is Date, so the correct merge code is %SetValues:Date%. Among the given choices, option A is the only one that uses the %...% delimiters, which are the standard for OmniStudio merge codes. Although the option contains a typographical error (the leading 'x') and uses a dot (.) instead of the standard colon (:) as a separator, it is the only choice that reflects the fundamental structure of a merge code. The other options represent entirely different and incorrect syntactical constructs for this context.

Why Incorrect

B. (‘ Setvalues’] [ ‘Date’]: This syntax resembles property access in languages like JavaScript, not the declarative merge code syntax used in OmniStudio Integration Procedures.
C. %SetValues Date: This option is syntactically incorrect. It lacks the required colon separator between the element name and the node, and it is missing the closing % delimiter.
D. {(SetValues. Date)}: This syntax, using curly braces, is associated with data binding in UI components like OmniStudio FlexCards or Lightning Web Components, not for server-side merge fields in an Integration Procedure's HTTP Action URL.

References

1. Salesforce OmniStudio Documentation

Integration Procedures: "Access Data in the Integration Procedure Data JSON". The documentation explicitly states the syntax for referencing a node from another element is %ElementName:PathToNode%. For example

%DRGetAccountDetails:Account:Name%. This confirms the colon separator and %...% delimiters.

2. Salesforce OmniStudio Documentation

HTTP Action for Integration Procedures: Under the "HTTP Path" configuration

the documentation provides examples like /account/%AccountId%/contacts

reinforcing that variables in the URL path must be enclosed in percent signs. This invalidates options B

C

and D which do not follow this primary rule.

Scroll to Top