Software Entitlement import error in CNTR number

Terry Marcus
Tera Contributor

Hi,

I’m using the Software Entitlement import capability in SAM Pro. I only use the ServiceNow template (samp_entitlement_import), I haven’t change it, but I'm pulling an error on all entitlements if I supply a Contract number. The error is saying that the “Contract number (CNTR…..) not found. Please enter a valid contract number.”, but the number is valid. All I have to do is copy and paste the number from the error message to the Contract number field and then run the import manually for each message to go away. I expect to see errors only when I’ve done something wrong not when I’ve done something right.

I’ve looked at the documentation multiple times but I’m not finding a solution. Can anyone help with this issue?

2 ACCEPTED SOLUTIONS

Ok, I found what is the issue, but I still cannot believe 🙂

On the contract record, there are two fields with numbers:

1. Number = CNTR

2. Contract number = long list of letters and numbers

And in the Software Entitlement import template, you need to use the #2 - Contract number, not Number.

Worked for me.

View solution in original post

Curtis_Myers
Tera Expert

in our instance Contract Number was relabeled Vendor Contract Number and number was relabeled Contract Number which contains the CNTR#

 

View solution in original post

4 REPLIES 4

Anna Palys
Tera Expert

Hi,

I'm experiencing exactly same issue.

Ok, I found what is the issue, but I still cannot believe 🙂

On the contract record, there are two fields with numbers:

1. Number = CNTR

2. Contract number = long list of letters and numbers

And in the Software Entitlement import template, you need to use the #2 - Contract number, not Number.

Worked for me.

Curtis_Myers
Tera Expert

in our instance Contract Number was relabeled Vendor Contract Number and number was relabeled Contract Number which contains the CNTR#

 

Curtis_Myers
Tera Expert

in our instance the Contract Number was labeled Vendor Contract Number and the number field was labeled Contract number which was causing the issue.