Advent of Code is back! Unwrap daily challenges to sharpen your Alteryx skills and earn badges along the way! Learn more now.
Community is experiencing an influx of spam. As we work toward a solution, please use the 'Notify Moderator' option on the ellipsis menu to flag inappropriate posts.
community Alteryx IO Mission Control
alteryx Community
Search
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Close
Free Trial

Alteryx Designer Desktop Ideas

Share your Designer Desktop product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Excel's #N/As read as zeros! UNACCEPTABLE!

Status: Implemented Submitted by 20 - Arcturus on ‎11-09-2015 05:27 AM
11 Comments (11 New)

The excel driver (.xlsx) converts these values to 0.  If you use the legacy excel driver (.xlsx) it brings in the #N/A values.  This issue was reported in the community and I am forwarding it to the New Idea as a problem that needs to be addressed on behalf of @JohnDoe.

See more ideas labeled with:
11 Comments
JohnDoe
8 - Asteroid
‎12-17-2015 03:03 AM

Actually, I have noticed that, after the 10.1 update, these excel errors are imported as nulls if the column has other records with numerical values, but are imported as text (the text "#N/A", etc. if they are in a column where other records are text strings!

0 Likes
Labels