apikey Issues with Bulk-Update Tool 4.11/4.12

[Jack Stanton]

Good Afternoon, 

Upon performing a test bulk update using the tool with a csv. with a single-entry record, I received some unexpected results. Usually the API key we always typically utilise is tied to our Database Manager’s user ID but unexpectedly the record "updated by" in the Audit History of the asset is showing “svc_servicemanager” alongside the date roughly the record was changed by the tool. The audit history is stating it's automatically updating the field "last audited date" without providing any input on the field through the JSON and then it indicates "Asset Last Updated date & user updated successfully:" in the audit logs even though this wasn't the intended updated field. Strangely the asset record DID update the desired field "model" but it doesn't show it having done so within the audit history when tried through 4.11.

When using 4.11

In Log file:
2025/04/16 12:48:43 [DEBUG] Processing Asset: ASSET NAME
2025/04/16 12:48:43 [DEBUG] Update Asset: ASSET NAME
2025/04/16 12:48:43 [DEBUG] Asset record updated successfully: ASSET ID
2025/04/16 12:48:43 [DEBUG] Asset record extended details updated successfully: ASSET ID
2025/04/16 12:48:43 [DEBUG] Asset Last Updated date & user updated successfully: ASSET ID

On Asset's Audit History:
Updated By “svc_servicemanager” 2025-04-16 12:14:45

Last Audited Date 2025-04-16 12:14:45

Nothing in Data Imports Guide - Configuration shows why this is happening or how to stop it all of a sudden and there doesn't appear to have been anything in 4.12 that would impact it as opposed to 4.11 within the change logs readme file. Also nothing on the "latest changes" page on Service Manager indicate the new version coming out either on March 18th? Due to the security risks posed by having an open API connection to GitHub for updates it's quite difficult too for us to see where issues might arise each time and whether the next update will fix it. Regardless i updated to 4.12 from 4.11 to see whether this would improve things however...

When using 4.12

After updating to 4.12 I'm getting even more sporadic results where it's now reporting that the record is being updated in the log file as follows:- 

2025/04/16 14:28:21 [DEBUG] Processing Asset: ASSET NAME
2025/04/16 14:28:21 [DEBUG] Update Asset: ASSET NAME
2025/04/16 14:28:22 [DEBUG] Asset record updated successfully: ASSET ID
2025/04/16 14:28:22 [DEBUG] Asset Last Updated date & user updated successfully: ASSET ID

and is now additionally showing:

2025/04/16 14:28:22  * Extended Record Skipped: 1

The Audit history on the Asset is now completely Unchanged since the update in 4.11. Is there a bug with this side that could be causing this issue? Really struggling to see what's being performed that's wrong here. I "could" still try and push the update for the additional 2000 or so entries but don't want to do so if we don't have a consistent audit history against the asset record due to legislative requirement etc. 

[Peter Clough]

+1 for getting this looked at please.

[Joshua Howitt]

Hi @Jack Stanton, looking through the changes included in patch 4.11 and 4.12 the CSV functionality should not have been effected. I will have a look at anything that could be causing this issue and get back to you here. 
Just to confirm you are facing this issue with CSV bulk imports?

[Jack Stanton]

Hi Josh,

It's CSV bulk import updates that I've been experiencing an issue with. Many thanks. 

[Joshua Howitt]

Hi @Jack Stanton,

I wanted to check in as I have been investigating the issue with the CSV bilk import updates. While I have been doing this a release has gone live to the Asset Import tool and version 4.13.0 is available for use. This was to resolve issues that were causing some issues around the asset class 'Network Circuit', 'Data Processing Record', and 'System'. Were the records you were having issues with related to these Asset Classes? Additionally, I have checked the releases and no changes in release 4.11 or 4.12 included any changes to the CSV bulk import functionality. Could you please update to version 4.13 and let me know if the problem persists?

[Jack Stanton]

Hi @Joshua Howitt,

Has this been published to Github yet? Just looking and can't see, is it still on there as v4.12? Many thanks.

[Joshua Howitt]

Hi @Jack Stanton, apologies it is currently being tested and should be released soon. I will update you here when v4.13 goes live. 

[Joshua Howitt]

Hi @Jack Stanton, version 4.13 should be available for use now. Please let me know if you have any issues with the latest released version.

[Jack Stanton]

Hi @Joshua Howitt, tried 4.13 and still showing the same issue, 

- Seems to be updating the field required, but not reflecting this in the log or audit history accurately.
- It's Updating "Last Updated date & user" without being prompted to update these fields in the Json. stating:- "[DEBUG] Asset Last Updated date & user updated successfully:"
- It's showing "Extended Record Skipped: 1" against the asset
- Since updating, it's now showing an incorrect date/time in the "audit history" against the asset on the CMDB. "svc_servicemanager (2025-05-03 19:00:19)"


It's on a device within the CMDB that isn't one of the ones you specified above with the Class being "Mobile Device", i'm just trying to amend the model field to a value specified in the csv. against the name field as a key ID. 

[Steve Giller]

1 minute ago, Jack Stanton said:

It's Updating "Last Updated date & user" without being prompted to update these fields in the Json.

If you've updated it with the import tool, that will change "Last updated date" because it's been updated. It will also update "Last updated by" because it was updated by the tool.

[Jack Stanton]

Hey Steve, 

Apologies, I may not have made it fully clear.

It changes the "Last Audited Date" on the asset record to what it believes to be "Last updated date" as indicated by the tools function against the record which is wrong, providing inaccurate data against our asset records. We aren't auditing the device by updating their records via csv. and we have separate considerations for what we in our organisation deem to be a device audit, i.e.: having users report to us on their devices for ownership and their status, our department performing inspections, stock counts, health checks etc. and the field has historically been updated when these activities take place.

A device moving state/sub-state or having a single value amended in it's record does not constitute an audit in our processes. I don't understand why the "Last Audited Date" is automatically set on the asset record if we don't need/want it to be and why this can't just be controlled like every other field update which can be controlled through the tool. I can't find records anywhere of this being introduced in the change logs either.

Primarily what I don't understand is why it's not showing up in the audit history as updating the "model" field since that is the only field which i had set out to update via the tool in this instance. Having the audit history be an accurate representation is useful for us to know if we've had the desired effect against the record on the CMDB as an additional measure separate from the log file. 

 

[Joshua Howitt]

Hi @Jack Stanton,

Could i please see an example of your Config file you are using for the Asset import, in addition to a full copy of your log with the import tool running in debug mode?
If you would prefer you can send it to my email address, 'joshua.howitt@hornbill.com'