Creating a new Model Category: Allow pre-allocated, Allow in bundle, and Allow as main not checkable

[HrishabhKumar]

I'm creating a new Model category for a custom child table extending the Configuration table. I'm unable to check the 'Allow pre-allocated', 'Allow in bundle', 'Allow as main', and 'Enforce CI verification' options on the model category form.

Whenever I check them and save the form, the options are unchecked automatically.

[Nilesh Pol]

@HrishabhKumar 

Hi, is custom model category extends alm_hardware table?

there are OOTB business rules on model category table, *validate model category and *normalize model category fields, you investigate this by reviewing it.

[ChallaR]

Hi @HrishabhKumar ,

you ca try below troubleshooting -

1. Missing Product Model Class Mapping

In the Enterprise Asset Configuration section, the Product model class is set to -- None --. This field is crucial for enabling those checkboxes.

Fix:
Set the Product model class to a valid class that extends alm_product_model. If your custom CI class doesn't have a corresponding product model class, you may need to create one.

2. Custom Table Not Properly Mapped

Your custom table (u_wireless_controller) must be properly mapped to both:

• A CI class (which you’ve done)
• An Asset class (you’ve selected alm_hardware)
• A Product model class (missing)

Fix:
Ensure your custom table is extended from both cmdb_ci and alm_asset (or related asset table), and that it has a corresponding product model class.

3. Dictionary Configuration

Sometimes, the dictionary attributes or ACLs on the fields can prevent editing.

Fix:
Check the dictionary settings for the Model Category table and ensure the fields are editable for your role.

---

 Steps to Resolve

1. Go to Model Category > open your record.
2. In Enterprise Asset Configuration, set a valid Product model class.
3. Save the record.
4. Reopen it — the checkboxes should now be enabled.

please mark as correct and close the thread if this is helpful. 

Thanks,

Rithika.ch