Service Portal Log (sp_log) records are missing the value for ID field.Issue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Overview This article explains why the ID field in sp_portal records can be empty most of the times. Empty ID values in Service Portal Log records Broadly speaking an expected behaviour. The only time that this field will be populated is when a user searching for something on Service Portal clicks on the results returned from the typeahead search dropdown and goes to the result directly. If the user types in a query and press enter or clicks on the search icon and navigate to the search result page, then the ID field will not be populated and will remain empty. Example Below is are examples of the two scenarios explained above and the resulting entries in sp_log: ID populated: Resulting Log: ID empty: Resulting Log: