State Field in alm_license table in SAM Pro

[anandsaurabh47]

Hi,

I see "state" field is mandatory field and hence throwing an error while importing the entitlements through entitlement import template.

I can add this column in the template and update the value as "Build" and fix the error but I am assuming if this field is mandate, then isn't it supposed to be part of the OOB entitlement import template?

Please help, I am using ServiceNow Zurich and using the latest entitlement import template available in Zurich.

[Ankur Bawiskar]

@anandsaurabh47 

not sure if this is a miss from ServiceNow side

But as a workaround you can use onBefore transform script and set the default value

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Ankur Bawiskar]

@anandsaurabh47 

Hope you are doing good.

Did my reply answer your question?

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[anandsaurabh47]

Hey Ankur, seems this field is set as mandatory by our developers here hence, it's throwing the error. But by default it's not.

[SAMfluencer · Accepted solution]

Hi @anandsaurabh47 ,

I checked this in my instance also on Zurich. I used the OOB import template and the entitlement imported successfully, defaulting to "In use" automatically.

The OOB entitlement import transform handles state (install_status) silently in the background 

Want to check if this is the root cause in your instance? Navigate to the  alm_license.LIST  table → Configure → All → open the Dictionary entry for the State column (install_status) → check if Mandatory is checked. If it is, uncheck it and try importing again that should resolve the error.

For reference, OOB this field is not mandatory at the dictionary level, so if it's checked in your instance it's likely been customised at some point.

If this helped - amazing, you're welcome, go click Helpful and Accept as Solution. If it didn't - well, at least you learned what not to do. Either way, we grow. 

Cheers, Abby

ITAM Principal Solution Architect