List view fields are blank after data import

[mcconnellsj]

Hi

We had a requirement to update a custom field in the location table: cmn_location.

The import set was a basic match of sys_id and the custom field.

When I ran the import set, I selected coalesce on the sys_id.

The import ran without error.  But when the cmn_location table is now viewed in a list, all (and I mean all) fields show "empty".  However opening each location shows it is fine, with all fields including the custom field intact.  If I dot walk to those fields from another table (eg Asset), the fields also appear okay int he list.

The records that were not referenced in the import are unaffected.

How can I reinstate the fields in the view?  I really don't want to import these records and start over, as too many dependencies within our instance and also external systems, the existing sys_id of these records must be maintained.

Thanks in advance.

[mcconnellsj]

Hi thanks for the suggestion.

I am not sure how to check for a conflict.

The ACLs for the cmn_location table have had no updates for 6 months.

The issue only affects the records that were updated by the import.

Can you give me some guidance on what to look for?

Thanks

[mcconnellsj]

Hi - can you be clear what on I would configure on a new read ACL?  I am struggling a little to work out your fix - would really appreciate it - thanks in advance.

Note once more that the only records affected are those updated by the data import.

[mcconnellsj · Accepted solution]

Hi all

Fixed

The issue is that the import set had sys_id's in UPPER CASE.

Not entirely sure what this does, blows the indexing somehow - the import set will claim "success" which is also weird.

The fix?  Simply re-run the previous import set with similar data but has sys_id in lower case - bingo - the records can be viewed in the list again like nothing happened.

If anyone can explain this one I would be interested.

Thanks to all who responded.