During testing, a merge code %Details:Customer|0:ID% does not display the ID. Which change correctly references the first item’s ID when the data path uses a 1-based index?

During testing, a merge code %Details:Customer|0:ID% does not display the ID. Which change correctly references the first item’s ID when the data path uses a 1-based index?

• A. To %Details:Customer|1:ID%
• B. To %Details:Customer|n:ID%
• C. To $Details:Customer|0:ID$
• D. To %%Details:Customer|0:ID%%

Answer: (A)

Indexing a collection in a merge path is 1-based, so the first item sits at position 1. With a 1-based index, referencing the first customer’s ID uses 1, giving %Details:Customer|1:ID%. Using 0 points to a non-existent element, so nothing is shown. The other formats don’t follow the required merge field syntax for this path and won’t correctly pull the first item’s ID. So the correct change is to use 1 as the index.

Indexing a collection in a merge path is 1-based, so the first item sits at position 1. With a 1-based index, referencing the first customer’s ID uses 1, giving %Details:Customer|1:ID%. Using 0 points to a non-existent element, so nothing is shown. The other formats don’t follow the required merge field syntax for this path and won’t correctly pull the first item’s ID. So the correct change is to use 1 as the index.