Issue Service Graph Connector for Operational Technology (Excel) Washington DC and Xanadu

[Twan]

Hi,
I'm using the ootb Service Graph Connector for Operational Technology (Excel) with the same import file. In Washington DC all assets load as expected, PLC's are in the correct tables. Attributes fields contain data as well "OT display name", "OT device type", "SIte" contain info.

When loading the same excel in Xanadu, it is importing the assets in 'cmdb_ci_ot' etc but the "OT display name", "OT device type", "SIte" are empty. Related to it it the Industrial Workspace is not showing the OT devices.

Have Xanadu running in two ootb instances both have the same issue. 

Does anyone have an explanation for this and know how to solve it? 

[Viraj Hudlikar]

Hello @Twan 

First of all, check the plugin is updated. 

Next do you have any configuration done over staging table and it has wiped out after upgrade of instance?

Are you using old excel template still then it can issue with column names, so grab new excel template from "sg_ot_excel_staging" table.

From IntegrationHub ETL module did you cross check by doing dry run for data source "SG-OT Asset Excel Import" which will help you to understand if any mapping is cleared out or has been removed.

In our case when we implemented OT module our client instance was in Utah version and when instance was upgraded to Washington DC at that time, ServiceNow made multiple changes in OOTB scripts and column name changes which had data upload issues latter as our ootb script were customize as per process need and new feature which was released by plugin were missing and it stop upload of data.

As you are stating you have two OOTB instance which I believe may be PDI and if this issue is really persisting then it would be better to raise a HI case as it would be product bug. 

If my response has helped you hit helpful button and if your concern is solved do mark my response as correct.

Thanks & Regards
Viraj Hudlikar.

[Twan]

Thanks for your reply, it did unfortunately not solved my issues so in raised a case.

One thing which is different I upgraded CMDB CI Class Models from version 1.64.0 to 1.69.0.
Not sure if this has any impact, I did mention it in the case as well.