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
ARich
Alteryx Alumni (Retired)
‎11-09-2015 10:13 AM
Status changed to: Coming Soon

This is part of the 10.1 release. Alteryx will read error strings from Excel as nulls, so as not to convert numeric type columns to string type columns.

 

Thanks for submitting, Marquee!

0 Likes
MarqueeCrew
20 - Arcturus
20 - Arcturus
‎11-09-2015 07:00 PM

Thanks for the update!

0 Likes
JohnDoe
8 - Asteroid
‎11-11-2015 07:05 AM

Alex, thank you for the update. However, the point is NOT that numerical columns are read as strings. The point is that error values in numerical columns are read as zero, which is way worse because it fundamentally changes the data. Would anyone possibly care to elavborate how Alteryx could have possibly messed up so much, and why I should trust Alteryx isn't guilty of other colossal errors elsewhere???

0 Likes
Cristian
9 - Comet
‎12-14-2015 01:04 AM

AlexP,

 

Alteryx 10.1 has been released, could you please let us know that the issue was ironed out?

 

Thank you.

 

Regards,

Cristian.

0 Likes
JohnDoe
8 - Asteroid
‎12-16-2015 09:40 AM

Cristian,

 

when updating, the software uninstalled the previous version, and in doing so lost all licence data. I tried to use the same license file I was sent last time, but it is not recognised.

 

I am now waiting for tech support to get their act together and sort this out.  It is simply ridicolous and reflects extremely poorly on Alteryx. Is it too much to ask not to spend a day reactivating your licence after an update? Why on earth did the update not recognise the license? When I first installed Alteryx it took 2-3 days and multiple attempts to finally receive a working licence from Alteryx. What a joke!

 

0 Likes
MarqueeCrew
20 - Arcturus
20 - Arcturus
‎12-16-2015 10:27 AM

John,

 

has your licensing issue been resolved?  If not, would you like some help from me?

0 Likes
ARich
Alteryx Alumni (Retired)
‎12-16-2015 06:35 PM
Status changed to: Implemented
 
0 Likes
ARich
Alteryx Alumni (Retired)
‎12-16-2015 06:37 PM
Status changed to: Implemented

With the 10.1 release, error strings in Excel are read as nulls, not zeros.

0 Likes
MarqueeCrew
20 - Arcturus
20 - Arcturus
‎12-16-2015 06:37 PM

Great news!  Thanks for the update. 

0 Likes
JohnDoe
8 - Asteroid
‎12-17-2015 01:16 AM

I have received a new licence file and it works.

I created a test spreadsheet with these errors:

  • division by zero
  • #name (I intentionally used a non-existing formula, e.g. MyRandomFormula(1,2,3)
  • #n/a (vlookup with no match)
  • #value (summing two cells containing text)

They are all imported as nulls now. Finally!

0 Likes
Labels