Software Entitlement Import Template Additional Fields

[Tom Frasure]

Software Entitlement Import Template - I can add an additional field call Tax % to the template and the import process will accept it even though it is not part of the template. I can't however do that with Hosting type field or other fields like IT Owner. Is there a way to update these fields using the template? I've tried to find information on knowledge documentation but haven't found anything related to this topic. 

[Community Alums]

Not sure whether you saw this KB- 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0854431

[Tom Frasure]

I hadn't seen this specific document but I have added a custom field (Tax%) to the import template which worked perfectly. The fields I was trying to update are in the Software Model table which I'm guessing I can't update either because of my access rights to that table or you can't populate a field that requires selections (Example: in the Host type field there are 3 choices to choose from).

[Tom Frasure]

Just to check I ran a test based on the instructions in the document and the error spelled it out to me that the fields don't exist in the Entitlement table which doesn't give me the ability to click on the tab to correct the column. But it's strange the Tax% appears there but it is in the entitlement table... lol 

[Daniel Slocum]

Hi Tom,

It is best if you import just the values available in the out-of-box template while being sure to populate a unique value into the AssetTag attribute.

Once you've completed the import, and have resolved any Entitlement Import Error records, you can then use an Import Set to import data to fill in additional values such as your Tax %, or any other custom columns you've added to the entitlement record or related records. 

I realize it is an extra step, but it is the best method for success.  In most cases across the platform, when an additional value is found within a source file, the platform will accept that value and drop it into the import table where values are stored before mapping to a destination table.  This is not the case with the Entitlement Import process in the SAM application as that process is customized just for the SAM use case. it doesn't follow the standard import methodology used elsewhere on the platform.