matthiask82,
Can you let us know the name of the location that's not working?

Thanks!

Hi!

It's called "Dynastica", I just re-added it and confirmed that the issue still exists. At one point in time, lists from the RTM account "dynastica" was shared to me, perhaps that's a clue?

Thanks!

matthiask82,
I've added this to our list to investigate; sorry for the inconvenience in the meantime.

Thanks!

I can report same problem. In my account it does not parse @Doma location in SmartAdd.

beny,
That's also on our list to investigate; sorry for the inconvenience.

Ditto - my RTM doesn't parse the @Cambridge location.

(All other locations work fine - apologies for double post)

Thanks scubbo; I've added that to our list to investigate.

Hello, I have @Doma location too and it doesnt work.
So I did a few tests and it seems that there is bug in parsing.
Everytime when location is ending to "a" @ smart add doesnt work for me.

dangar,
Thanks for your feedback; I've added that to our list to investigate too.

Interestingly, I also have problems with one location, and that also ends with an "a" (@hemma)

rajjan,
Thanks for that additional location; I've added that also.

I'm curious about other locations that don't work, and especially curious if anyone has any locations that end in 'a' that do work.

I also have a location called @Hemma that doesn't work.

86daia,
I've added this one as well. Thanks for the input.

I think hangar got it. I'm using RTM in pt-br and smart add doesn't parse the locations @casa and @rua.

mfandrade,
Thanks for the additional information on this.

I have that happening for all my locations - smartadd doesn't parse.

Would be nice if that would be fixed.
Until then I email everything in. That still works.

johenkel

johenkel,
If none of your locations at all are being parsed, there may be something else going on. Would it be possible to submit a Smart Add issue report via our support system? We'd love to take a closer look.

Thanks!

Hi brendan,
I just checked them.
I got about 23 locations that have a number as name and 5 that have words. The words work, but the numbers don't.
I had emailed the support about 8 month back and they had suggested, that I change all my location names into words. Sounds easier than done, we use numbers for all our locations not only in RTM. It would create a hurdle in communications for my company.

Do you have any idea how I can get that to work?

johenkel

johenkel,
Location names can contain numbers, but they can't consist of a number alone. Sorry for any inconvenience.

In the meantime, you should be able to rename the location name to "Site 4", for example, so that the number will correspond to your other systems.

Hope that helps!

Same problem with @jpmc-de in my account :-(

Now I'm having this problem with: @shop

We have (finally!) been able to track this one down -- it was happening in certain circumstances for locations that begin with the '@' character and contained particular letters.

It should be fixed now -- please reload the web app, and let us know if you continue to experience problems.

Emily, it was fixed for me. Thanks!

FYI, Now I've made an additional test with the problematic locations I reported 4 weeks earlier (@casa and @rua, in portuguese) and they're working now! Thanks a lot.