INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Use of commas in custom field names [Resolved]  (Read 738 times)

jelyon

  • Recent member
  • *
  • Posts: 7
Use of commas in custom field names [Resolved]
« on: June 01, 2014, 04:51:56 pm »

So I've used commas in custom field names, not seeing anything specifically prohibiting that.

Now when I use those fields in an expression, I don't get the full field. For example: My field might be "Charts: Track, Date Charted"

What I see though in my expression once it's been evaluated is "Charts: Track".

Is this behavior by design, an oversight, or a bug?

Thanks!
Logged

MrC

  • Citizen of the Universe
  • *****
  • Posts: 10462
  • Your life is short. Give me your money.
Re: Use of commas in custom field names
« Reply #1 on: June 01, 2014, 08:48:10 pm »

I would think that [ ] have higher precedence than , so that fields are tokenized above function arguments, but there could be a bug here.  I haven't spent time looking at these edge cases.  See if escaping the comma with a forward slash helps.
Logged
The opinions I express represent my own folly.

jelyon

  • Recent member
  • *
  • Posts: 7
Re: Use of commas in custom field names
« Reply #2 on: June 02, 2014, 06:16:01 am »

Escaping the comma works perfectly.

Thank you!
Logged
Pages: [1]   Go Up