Alteryx Designer Ideas

Share your Designer product ideas - we're listening!
Alteryx is here to help you solve your biggest data challenges. Read about the new Virtual Solution Center here.

Field Name Conventions

Some say to mato and some say to_mato, but how about:  to/mato?

 

While working with my new friend, @cedric we ran across a field in his data that contained a '/' character.  We were building a macro where we updated the value of the field [AB/CD] with another field selected from the incoming data.  Our error message was something akin to:  Field AB was not found.

 

We worked around the issue, but what remained was the fact that certain characters are permitted in field names within some aspects of Alteryx and not in others.  I don't know if you're aware of this limitation.  

 

Cheers,

Mark

4 Comments
Status changed to: Inactive
 

The status of this idea has been changed to 'Inactive'. This status indicates that:

 

1. The idea has not had activity in the form of likes or comments in over a year.

2. The idea has not reached ten likes.

3. The idea is still in the 'New Idea' status. 

 

However, this doesn't mean your idea won't be implemented! The Community can still like and comment on this idea. With enough renewed interest, this idea can be brought back into the 'New Idea' status. 

 

Thank you for contributing to the Alteryx Community and the Alteryx Product Idea Boards!

11 - Bolide
11 - Bolide

Interesting .. @MarqueeCrew any idea about the scope of permitted special characters 

10 - Fireball
10 - Fireball

interesting Mark, have you retested recently? a workflow to test / show this here would be useful for us to see what was happening and what we need to watch out for.