Lattice demographic data error custom attributes missing from survey filters

Not specified by the original author.

TL;DR

Fix this in Lattice by acting on the exact problem first: trace one affected filter in Lattice from the survey audience export back to the attribute source, find whether the attribute was renamed, deleted or had its field type changed after the survey audience was built, rebuild the audience with the corrected attribute mapping, and retest the filter on the affected survey before sharing filtered results. Do not rerun the same survey, report or export unchanged, because the same inputs produce the same failure. Prove the fix on one survey, team or department first, then rerun the full scope and reconcile the results.

how to fix Lattice demographic data error custom attributes missing from survey filters fails error

Use this when

• The operation in Lattice fails with this exact problem: how to fix Lattice demographic data error custom attributes missing from survey filters fails error.
• The same failure repeats on retry with unchanged inputs.
• A survey launch, results dashboard, manager report or action plan is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with an interpretation call such as which driver to prioritise. That is a people analytics judgement, not this failure.

Steps

1. Reproduce the failure on one named survey, team or department in Lattice and record the full problem text plus the survey, team or period involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: trace one affected filter in Lattice from the survey audience export back to the attribute source, find whether the attribute was renamed, deleted or had its field type changed after the survey audience was built, rebuild the audience with the corrected attribute mapping, and retest the filter on the affected survey before sharing filtered results. Verify: the single failing survey, team or department now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring surveys, teams or departments that share the same distribution list, roster sync or dashboard, because this class of failure rarely affects only one group. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Lattice on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the raw response record, the HR roster record or the survey platform record, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the survey run log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

how to fix Lattice demographic data error custom attributes missing from survey filters fails error

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single group proof, then the full rerun.

How to fix - how to fix Lattice demographic data error custom attributes missing from survey filters fails error

The how to phrasing for the same failure in Lattice. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Lattice troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

A mid cycle attribute change breaks the mapping for surveys launched before the change, so the filter shows missing while new audiences built after the change work fine, and only rebuilding the audience fixes the old survey.

Edge cases

• The survey was reopened, the roster was resynced or a team was restructured after the failing run started. Refresh the survey state and reapply the fix against the current values, not the values from the failed run.
• The single group proof passes but the full rerun still fails on other groups. Treat each remaining failure as its own scope, because a shared distribution list or dashboard can hide more than one cause.
• The source systems disagree on the correct value. The raw response record governs response counts, the HR roster governs who was invited, and the platform record governs what was sent or shown; record which source won and why.

Compatibility: Lattice at current versions, plus the survey platform, roster or reporting tool the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_xF-LSjAMWLO0LrpzdjkeRg

Resolved from the public thread: https://vectle.com/posts/pst_xF-LSjAMWLO0LrpzdjkeRg

Thread query: how to fix Lattice demographic data error custom attributes missing from survey filters fails error

TL;DR: Fix this in Lattice by acting on the exact problem first: trace one affected filter in Lattice from the survey audience export back to the attribute source, find whether the attribute was renamed, deleted or had its field type changed after the survey audience was built, rebuild the audience with the corrected attribute mapping, and retest the filter on the affected survey before sharing filtered results. Do not rerun the same survey, report or export unchanged, because the same inputs produce the same failure. Prove the fix on one survey, team or department first, then rerun the full scope an

Not specified by the original author.

TL;DR

Fix this in Lattice by acting on the exact problem first: in Lattice, open the survey filter settings, check the custom attributes are marked visible for survey filtering, confirm each attribute has values populated on the survey audience records rather than only in the people directory, repopulate or resync the missing attributes, and test the filter on one attribute with known employees before rebuilding the results view. Do not rerun the same survey, report or export unchanged, because the same inputs produce the same failure. Prove the fix on one survey, team or department first, then rerun the full scope and reconcile the results.

Lattice demographic data error custom attributes missing from survey filters

Use this when

• The operation in Lattice fails with this exact problem: Lattice demographic data error custom attributes missing from survey filters.
• The same failure repeats on retry with unchanged inputs.
• A survey launch, results dashboard, manager report or action plan is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with an interpretation call such as which driver to prioritise. That is a people analytics judgement, not this failure.

Steps

1. Reproduce the failure on one named survey, team or department in Lattice and record the full problem text plus the survey, team or period involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: in Lattice, open the survey filter settings, check the custom attributes are marked visible for survey filtering, confirm each attribute has values populated on the survey audience records rather than only in the people directory, repopulate or resync the missing attributes, and test the filter on one attribute with known employees before rebuilding the results view. Verify: the single failing survey, team or department now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring surveys, teams or departments that share the same distribution list, roster sync or dashboard, because this class of failure rarely affects only one group. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Lattice on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the raw response record, the HR roster record or the survey platform record, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the survey run log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

Lattice demographic data error custom attributes missing from survey filters

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single group proof, then the full rerun.

How to fix - Lattice demographic data error custom attributes missing from survey filters

The how to phrasing for the same failure in Lattice. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Lattice troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

Lattice survey filters read the attribute values carried on the survey audience record, so attributes that exist in the directory but were never synced to the survey audience appear missing from every filter.

Edge cases

• The survey was reopened, the roster was resynced or a team was restructured after the failing run started. Refresh the survey state and reapply the fix against the current values, not the values from the failed run.
• The single group proof passes but the full rerun still fails on other groups. Treat each remaining failure as its own scope, because a shared distribution list or dashboard can hide more than one cause.
• The source systems disagree on the correct value. The raw response record governs response counts, the HR roster governs who was invited, and the platform record governs what was sent or shown; record which source won and why.

Compatibility: Lattice at current versions, plus the survey platform, roster or reporting tool the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_-8WU7eyInCgMRKvZKAgc6g

Resolved from the public thread: https://vectle.com/posts/pst_-8WU7eyInCgMRKvZKAgc6g

Thread query: Lattice demographic data error custom attributes missing from survey filters

TL;DR: Fix this in Lattice by acting on the exact problem first: in Lattice, open the survey filter settings, check the custom attributes are marked visible for survey filtering, confirm each attribute has values populated on the survey audience records rather than only in the people directory, repopulate or resync the missing attributes, and test the filter on one attribute with known employees before rebuilding the results view. Do not rerun the same survey, report or export unchanged, because the same inputs produce the same failure. Prove the fix on one survey, team or department first, then reru

Not specified by the original author.

TL;DR

Fix this in Lattice by acting on the exact problem first: in Lattice, open the survey language settings, confirm the Spanish translations are complete for every question including questions added after translation, check the respondent language preference is set to Spanish for the affected group, republish the survey after completing the missing translations, and preview as a Spanish respondent before resending invitations. Do not rerun the same survey, report or export unchanged, because the same inputs produce the same failure. Prove the fix on one survey, team or department first, then rerun the full scope and reconcile the results.

Lattice survey multilingual error Spanish version shows English questions

Use this when

• The operation in Lattice fails with this exact problem: Lattice survey multilingual error Spanish version shows English questions.
• The same failure repeats on retry with unchanged inputs.
• A survey launch, results dashboard, manager report or action plan is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with an interpretation call such as which driver to prioritise. That is a people analytics judgement, not this failure.

Steps

1. Reproduce the failure on one named survey, team or department in Lattice and record the full problem text plus the survey, team or period involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: in Lattice, open the survey language settings, confirm the Spanish translations are complete for every question including questions added after translation, check the respondent language preference is set to Spanish for the affected group, republish the survey after completing the missing translations, and preview as a Spanish respondent before resending invitations. Verify: the single failing survey, team or department now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring surveys, teams or departments that share the same distribution list, roster sync or dashboard, because this class of failure rarely affects only one group. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Lattice on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the raw response record, the HR roster record or the survey platform record, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the survey run log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

Lattice survey multilingual error Spanish version shows English questions

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single group proof, then the full rerun.

How to fix - Lattice survey multilingual error Spanish version shows English questions

The how to phrasing for the same failure in Lattice. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Lattice troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

Questions added or edited after the translation step show in the default language, so a partly translated survey shows English for exactly the questions touched after translation.

Edge cases

• The survey was reopened, the roster was resynced or a team was restructured after the failing run started. Refresh the survey state and reapply the fix against the current values, not the values from the failed run.
• The single group proof passes but the full rerun still fails on other groups. Treat each remaining failure as its own scope, because a shared distribution list or dashboard can hide more than one cause.
• The source systems disagree on the correct value. The raw response record governs response counts, the HR roster governs who was invited, and the platform record governs what was sent or shown; record which source won and why.

Compatibility: Lattice at current versions, plus the survey platform, roster or reporting tool the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_6e6KMBBllcaCnC-2CLMHBA

Resolved from the public thread: https://vectle.com/posts/pst_6e6KMBBllcaCnC-2CLMHBA

Thread query: Lattice survey multilingual error Spanish version shows English questions

TL;DR: Fix this in Lattice by acting on the exact problem first: in Lattice, open the survey language settings, confirm the Spanish translations are complete for every question including questions added after translation, check the respondent language preference is set to Spanish for the affected group, republish the survey after completing the missing translations, and preview as a Spanish respondent before resending invitations. Do not rerun the same survey, report or export unchanged, because the same inputs produce the same failure. Prove the fix on one survey, team or department first, then reru