I need your help in one of the requirement. I am working on one non 834 Benfit file where we are sending Medical coverages in that.

Originally replied by Brenda Sutton on Mar 26, 2026, 9:38 AM.

@Aman Gaur​,

This is almost always a data context / array-scope issue, not a “tier code” issue.

Your plan_coveragelevel mapping is working for the subscriber because the subscriber row is the one where the medical plan election actually exists. In Dayforce, when a field lives inside an array, Integration Studio only has one clear value if the mapping is looking at the correct record in the correct array. If the path travels through an array and there are multiple possible elements, the value can’t be resolved the same way unless you explicitly select the right record or map from the right parent context.

What is happening in your example is likely this:

• Subscriber has the employee’s own benefit election, so plan_xrefcode matches and plan_coveragelevel returns FAM_BCBS_OF_IL_PPO_1.
• Child and Spouse are coming from a different dependent loop / dependent context, and that row does not have the same plan election field available in that location.
• So the dependent rows have no matching source value, and both Medical plan name and medical tier come out blank.

The docs call out two important rules here: source arrays and nested arrays have to be handled in the right context, and when a field can have more than one possible record, Integration Studio expects you to use a filter/Choose Record-style selection so it can return one unique value. It also notes that array-based mappings are sensitive to the structure of the source data and destination parent/child arrangement.

What to check

Look at the source path for the dependent row and confirm whether plan_xrefcode and plan_coveragelevel are actually available under that dependent node. In many benefit exports, dependent rows do not carry the same plan election object as the employee row; they only inherit relationship data, while the coverage data remains on the employee election object. That means the mapping must either:

• pull the coverage from the employee election and reuse it for dependents, or
• point the dependent mapping at the dependent election array if the file structure truly has dependent-specific elections.

Most likely fix

If the dependents should show the same medical coverage as the subscriber, do not map plan_coveragelevel independently from the dependent record. Instead, carry the subscriber’s selected medical plan/tier down into the dependent segment using the employee-level election as the source.

In practice, that usually means one of these approaches:

• map the dependent row from the same employee election context as the subscriber, or
• use a parent-level expression / shared parent context so the dependent record inherits the employee’s medical plan and tier.

The guide specifically warns that when fields are repeated or nested under arrays, they must be mapped from the correct array context, and when you need a single matching record, you must constrain the selection so Integration Studio knows which item to use.

Why your current logic blanks dependents

Because your current condition is effectively saying: “only populate this if the current row’s plan_xrefcode is one of these BCBS medical plans.”

That works for the employee row, but the dependent row is probably not sitting on a record where that field exists, so the filter never resolves to a material value. In IDL terms, missing values propagate, so the output stays blank.

Let me know if this helps and works for you!

Brenda