<h2>[SAMP/Software Subscriptions] Maintaining manually imported data in Software Subscriptions (samp_sw_subscription) table</h2><br/><div style="overflow-x:auto"><article><div ><h3 >Issue </h3><section><ul style="list-style-position: inside;"><li>The manually imported data in Software Subscriptions (samp_sw_subscription) table gets cleaned/deleted post the "SAM - Import User Subscriptions" scheduled job run, whereas the Software Subscriptions created from the Integration Profile (Office 365) remains undeleted.</li></ul> <p style="padding-left: 120px;"><span style="font-family: 'courier new', courier;">https://<<instance_name>>.service-now.com/samp_sw_subscription_list.do</span></p> <p style="padding-left: 40px;"><img src="/sys_attachment.do?sys_id=1fdc17bcdb0078d066e0a345ca96193a" width="1075" height="198" /></p></section></div><div ><h3 >Release</h3><section><ul style="list-style-position: inside;"><li>Instance with Software Asset Management Professional plugin enabled.</li></ul></section></div><div ><h3 >Cause</h3><section><ul style="list-style-position: inside;"><li>When the value of the field "Source from integration" (sourced_from_integration) column is "null", then the record gets cleaned during the "SAM - Import User Subscriptions" import job run.</li></ul> <p style="padding-left: 40px;"><img src="/sys_attachment.do?sys_id=97dc17bcdb0078d066e0a345ca96193c" width="1060" height="376" /></p></section></div><div ><h3 >Resolution</h3><section><ul style="list-style-position: inside;"><li>In general, when the "<strong>SAM - Import User Subscriptions</strong>" scheduled job runs, it will clean out all records in the Software Subscriptions (samp_sw_subscription) table where the value of the field "Sourced from integration" (sourced_from_integration) column is "null".</li><li>"Null" also happens to be the default value of the column, so when importing into the subscription table, the value of "sourced_from_integration" needs to be explicitly set to 'No' to ensure that the records are retained post the scheduled job run.</li><li>This can be done by either setting this value with either a script in the transform map or including the value for the column in the source import file and mapping the value.</li></ul></section></div></article></div>