A specific Aurena page throws a 'Bad metadata error: The list [ListName] does not exist in dictionary' error as soon as you navigate to it, even though full access/projection permissions are already confirmed. What actually resolves this kind of metadata-mismatch error?

All FAQ questions / Platform, Aurena, and customization

Answer

This is typically caused by a stale or corrupted published configuration context for that page or projection, rather than an actual missing permission. Unpublishing and then republishing the relevant configuration context (the customization/configuration layer the page belongs to) has resolved this exact 'list does not exist in dictionary' symptom — effectively forcing the published metadata to be regenerated cleanly, rather than continuing to reference whatever stale/broken state was causing the error.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Platform, Aurena, and customization questions