Free Salesforce Plat-Dev-210 Actual Exam Questions s - Question 6 Discussion
What is the merge code syntax for passing a Date node from an element named SetValues in the
URL?
C/D? I’m between C and D as well. C’s %SetValues.Date% matches how I’ve seen variables merged in Integration Procedures, especially for simple node access. D’s colon syntax looks unusual to me, feels more like older or different contexts. Since the question is about a Date node specifically, dot notation (as in C) seems cleaner and clearer. Also, the percent signs are usually right for merge codes here. So I’m leaning more towards C because it fits the typical IP style I've worked with.
I think B fits the typical merge syntax for simple node values here. B
It’s C because the percent signs are commonly used for merging variables in Integration Procedures, especially with dot notation for child nodes. D’s colon syntax seems off here.
D imo, colon syntax fits Integration Procedure merge codes better.
B seems off since double braces are more for UI templates, not IP syntax.
D imo, colon syntax fits Integration Procedure conventions better than braces or brackets.
It’s D because the colon syntax is typically used in merge codes within Integration Procedures when referencing a node, especially if there are spaces or special characters involved. The %…% format is standard for IP merge codes, and adding the colon between the element and the field usually helps avoid ambiguity. B with double braces is more common in formulas or other contexts but not usually in HTTP Action URLs inside IPs. So D fits best here.
B imo, the double braces {{}} are standard for merge codes in IP URLs.
C/D? C is the classic syntax I’ve used for straightforward field access, but D’s colon might be necessary for nested nodes. It depends on how the element is structured in the IP.
D imo, the colon syntax (%SetValues: Date%) is often used in some Fusion environments for referencing element fields, especially when dealing with nodes rather than simple variables. It feels like a safer bet here since it explicitly points to the Date node inside SetValues. C is close but might not handle nested nodes as cleanly in all cases.
Pretty sure it’s option C: %SetValues.Date%. That’s the usual way to reference fields in URLs inside Integration Procedures.