Model Category is not equal to model Category

[devanshsing]

When I open an asset record that satisfied the below condition:  'CI Class' field of asset's 'Model Category' does not match to the class of the CI that is linked to the asset THEN I should be able to modify the 'Model Category' field of the asset.

Currently I have this requirement I am not able to understand that when I will face this scenario because When I create asset with model category let's say computer ci record for that asset is automatically get created by OOTB Schedule Job. 

[kaushal_snow]

@devanshsing ,

this is because the ci class doesn’t match the asset’s model category ci class.......this is because the model category drives how the ci and asset were first created and must stay consistent with those underlying mappings.......so in your scenario you won’t see that condition occur unless someone manually changed the ci class separately or the linked ci was assigned a class that doesn’t match the model category’s configured ci class..... and if you really need to handle that situation you’d typically build custom logic or validation to allow updating the model category rather than relying on oob behavior which assumes model category and ci class stay aligned.........

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.

[devanshsing]

Ok Understood  that @kaushal_snow  but can you please tell me how to approach to solve this scenario I have tried with UI Policy but it is not working actually.