question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Delimited File importer - doesn't accept full stops in the column headings

See original GitHub issue

Prerequisites

Description

The filter search option under the Run section on the Import from File Delimiter does not accept full stops in the column heading names. This is a relatively minor issue however the training material for new starters has a sample file with a full stop in the column name located here

Steps to Reproduce

  1. Download sample file for testing from the link above

  2. Click on Import from Delimited file

  3. Load specified file and confirm the file headers have a full stop in them such as source.Name

  4. Click in the search field above the attributes and enter search query, such as source.Name==“Greg” -> no results are shown

  5. Create a copy of the file and remove the full stop. Load file and Repeat the same query search without the full stop -> results are shown

Expected behaviour: results are returned for ile headers have a full stop in them

Actual behaviour: as per repro steps - no results are returned

Reproduces how often: 100%

Additional Information

image

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:8

github_iconTop GitHub Comments

1reaction
Auriga2commented, Sep 27, 2021

As a better fix, now the query allows trailing or leading white spaces in the column header.

0reactions
serpens24commented, Oct 17, 2021

I have copied the steps from above and executed. The functionlaity is working, ticket can be closed.

  1. Download sample file for testing from the link above - PASS
  2. Click on Import from Delimited file - PASS
  3. Load specified file and confirm the file headers have a full stop in them such as source.Name - PASS
  4. Click in the search field above the attributes and enter search query, such as source.Name==“Greg” - PASS, results ARE now found
  5. Mapped Type and Label attributes to source.Type and source.N?ame and performed an import - confirmed only Greg<Person> is imported in line with filter.
Read more comments on GitHub >

github_iconTop Results From Across the Web

CSV not parsed into columns despite Get Data delimiter set
My Excel does not parse CSV file correctly. The separator is comma (,). Even if I use the Get Data tool and set...
Read more >
6 Common CSV Import Errors and How to Fix Them - Flatfile
One of the most common CSV import errors is that the file is simply too large. That can be caused by too many...
Read more >
Avoid that space in column name is replaced with period ...
csv(filename,header=TRUE) , and then the space in variable names became ".", for example, a variable named Full Code became Full.Code in the ...
Read more >
Using R: common errors in table import - R-bloggers
I've written before about importing tabular text files into R, ... R will turn them to full stops), remove empty columns above and...
Read more >
Data Import error message reference - Analytics Help
Message Meaning So... Empty column header at column number X. The upload file is missing a column header. Ed... Multiple errors occurred: List of multiple...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found