# CSV import does not accurately detect non-blank entities

**URL:** <https://community.fibery.io/t/csv-import-does-not-accurately-detect-non-blank-entities/3280>\
**Category:** Bugs & Issues\
**Created:** [September 12, 2022, 9:49am UTC](https://community.fibery.io/t/csv-import-does-not-accurately-detect-non-blank-entities/3280 "2022-09-12T09:49:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![neil](https://avatars.discourse-cdn.com/v4/letter/n/839c29/32.png) [@neil](https://community.fibery.io/u/neil)\
**Post date:** [September 12, 2022, 9:49am UTC](https://community.fibery.io/t/csv-import-does-not-accurately-detect-non-blank-entities/3280/1 "2022-09-12T09:49:43Z")

</div>

It’s very nice that CSV import will try to find which rows have non-blank data, but it seems to get it wrong quite often. I imported a large CSV of our vendors and it missed half of the fields that actually had data in them. Actually it failed the import. For most of the fields that Fibery thought were empty, upon completing the import, the fields were in fact imported as empty in Fibery even though they do exist in the original CSV.

---

<div class="post-metadata">

**Author:** ![neil](https://avatars.discourse-cdn.com/v4/letter/n/839c29/32.png) [@neil](https://community.fibery.io/u/neil)\
**Post date:** [September 12, 2022, 9:56am UTC](https://community.fibery.io/t/csv-import-does-not-accurately-detect-non-blank-entities/3280/2 "2022-09-12T09:56:32Z")

</div>

Ah, it turns out this happens when the field name is repeated (as it apparently is when doing an export from Sage Intacct). This seems like something Fibery could check for and detect.