After a platform update to row-level security (RLS) implementation, generated access doesn't include all the code combinations we expect.

All FAQ questions / Reporting and analytics

Answer

Treat this as expected re-verification work after an RLS implementation change, not necessarily a bug — re-run the relevant generation procedure for the affected security model and compare the actual combinations produced against your maximum/wildcard authority settings before assuming records are being silently dropped.

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

← Browse Reporting and analytics questions