You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@glennmatthews Does it seem reasonable to just turn dynamic groups off this model for now? e.g. is_dynamic_group_associable_model = False on the model.
If you don't see a use case for dynamic groups of ConfigCompliance, absolutely that would be the appropriate fix. See also the note added in v2.3.6 release notes (we missed it in v2.3.0, sorry!):
App Developers should review the feature set of their data models and consider whether their models should opt into or out of inclusion in Dynamic Groups, Contacts/Teams, Object Metadata, and Saved Views via the inclusion or omission of appropriate model mixins and flag variables. Refer to the developer documentation for details.
Environment
Expected Behavior
I expected to be able to set the columns in the table view on the Config Compliance page
Observed Behavior
Steps to Reproduce
Issue originally reported via slack: https://networktocode.slack.com/archives/C01NWPK6WHL/p1727879954240279
Workaround
Since this issue can cause the Config Compliance view to be rendered inoperable, you can use the following steps to remediate the issue temporarily:
tables.ConfigComplianceTable.columns
and click Clear SelectedThe text was updated successfully, but these errors were encountered: