SOTI Pulse Logo

Adding an additional value to an Enumerator Custom Attribute

Solved
MS
Matt S
Union Pacific Railroad Company

I'm still learning the ropes after our former MobiControl admin retired, so apologies if this is a simple question.

We use a Custom Attribute to list out the different "usage types" in our inventory, and need to add an additional value to the list. I'd have expected to be able to do so via the Global Settings pane, but I'm unable to do so, as it says the field is already in use. I'm not modifying any of the existing entries, just adding a new one.

It seems like it'd be pretty limiting if one couldn't adjust the values at all after it's been set and in the field, so I feel like I'm missing something.

6 months ago
SOTI MobiControl
ANSWERS
RC
Raymond Chan Diamond Contributor
6 months ago

Enumerated custom attributes used to be modifiable without much restriction many years ago.  However, the situation has been changed a couple of years ago to ensure stability/robustness of deployed policies which involve custom attributes in their assignment filter(s).  Administrators will not be able to make changes for custom attribute involved in assignment filters, and get warning message that it is in use, and with details (subjected to CA permissions owned by the administrator attempting to make changes) of which device(s) and policies are using it.  

To make changes/additions, one has to temporarily remove its active usage in all existing assignment filter(s) first.  Modify custom attribute value of relevant devices using the new enumerated item(s), and then add back the custom attribute in the assignment filter(s) of relevant policies.   This revoking followed by re-deployment approach may not have significant side effect(s) for some policies. E.g. turning on USB storage feature-control for no more than 2 minutes before disallowing it again may be tolerable.  However, disabling lockdown menu for 20 minutes or longer may be a big security risk or impact to end-users' work-flow.

Even worse, if the affected policy involves app deployment, using the above approach may cause some apps to be uninstalled (and thus possible app data loss) when the custom attribute is temporarily removed from the assignment filter(s).  One workaround requiring much more work is to create a totally new custom attribute with all the new required enumerated fields, assign value to all devices (either manually, or imported in bulk with CSV, or programmatically with MobiControl API), and then modify the filter expression of each affected policy to use the new custom attribute. To ensure a safer transition, the last step may first involve using OR operator on both old and new custom attribute in the filter expression, followed by complete removal of the old custom attribute in a later stage.

In any case, attempting above change procedures require COMPLETE understanding of how & where the old custom attribute is used, possible side effect(s) of policy involved, careful planning, and pilot-run/tests of the procedures on non-production devices before full-scale changes to all production devices.

Solution
MS
Matt S
6 months ago

Appreciate the details, thanks

ZC
Zafer Cigdem
6 months ago

Hi Matt,

It looks like you have already have another Custom Attribute Called "USageType", so if you can try to rename the new one's name as for example UsageType2 or such, this should work, otherwise please let us know

Zafer

MS
Matt S
6 months ago

I tested this out by creating a new Enumeration attribute, assigning it to a device, and then attempting to add a new value. But I'm seeing the same error.

ZC
Zafer Cigdem
6 months ago

Looks like same issue, can you add 20250523 at the and of the name just for test purpose on your last example's name side.

Also Can you click on the "View details" section and share the output with us

I can see some space maybe it may cause an issue on your case, I can create Enum as follows well:

I hope this helps.

Zafer

MS
Matt S
6 months ago

Hi, I tried to edit the name but am seeing the same error. I also removed the spaces before each of the values. Attaching screenshots of this, and the "View Details" section.

ZC
Zafer Cigdem
6 months ago

Hi Matt,

I don't face this issue, so below is my estimation that may help:

Now this looks like a permission issue, if you are admin then you don't need to check out the user permission side but otherwise verify it from Hamburger Menu ->Users and permissions --> Users --> find your username --> click under Device Group permission side --> and "Edit custom Attribute Values" 

And just in case, from Global Settings --> Custom Attribute section click on the tripple dot left section of " TestEnumeration" --> permission and check your name on the list or not, for a double check you can remove your name and re-added as well. 

after this you can try to create a custom attribute without enable send the devices first maybe, to check whether it allows you to create (at least) and then you can update your new custom attribute to enable send devices options.

 I hope this helps.

MS
Matt S
6 months ago

My account has administrator permissions, so I don't think that's the issue.

It sounds like this might be a bug, so I'll open a ticket with our account rep. Thanks.

K
KSTMOD@SOTI
6 months ago

Hello Matt S,

Thank you for posting on SOTI Pulse.

And thank you to Zafer Cigdem and Raymond Chan for your helpful contributions — your expertise is always appreciated!

Just checking in to see if Raymond’s and Zafer's suggestion helped resolve your query regarding adding an additional value to an Enumerator Custom Attribute?

You may also find this helpful:
Custom Attributes

Note: You can select your MobiControl version from the top-right corner of the page to see the relevant instructions.

If you need any further assistance, feel free to reply — we’re happy to help!

Warm regards,
KTMOD

K
KSTMOD@SOTI
6 months ago

Hello Matt S,

We are glad that your issue is now resolved.

Warm regards,
KTMOD

Similar Discussions