# Cannot have @ in account name

**URL:** <https://forum.sambapos.com/t/cannot-have-in-account-name/15086>\
**Category:** V5 Issue\
**Created:** [June 11, 2017, 3:55am UTC](https://forum.sambapos.com/t/cannot-have-in-account-name/15086 "2017-06-11T03:55:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mjb2000](https://forum.sambapos.com/user_avatar/forum.sambapos.com/mjb2000/32/29209_2.png) [@mjb2000](https://forum.sambapos.com/u/mjb2000)\
**Post date:** [June 11, 2017, 3:55am UTC](https://forum.sambapos.com/t/cannot-have-in-account-name/15086/1 "2017-06-11T03:55:41Z")

</div>

As the title suggests, it doesn’t seem to be possible to have account names containing an `@` symbol. Although the account mainly works as expected, when trying to navigate to the account using a `Navigate Module` action the user is actually taken to the main accounts overview, rather than the specific account I wanted to show.

**This is dangerous** because I don’t want all my users being able to see all accounts. Clearly I can change the naming of my accounts to use the name instead of email address, but even if I do so, if an operator created a new customer with an `@` randomly in their name and then used some form of automation that I had created with a good intention, they will find themselves with access to all accounts…

---

<div class="post-metadata">

**Author:** ![JTRTech](https://forum.sambapos.com/user_avatar/forum.sambapos.com/jtrtech/32/21270_2.png) [@JTRTech](https://forum.sambapos.com/u/JTRTech)\
**Post date:** [June 11, 2017, 12:00pm UTC](https://forum.sambapos.com/t/cannot-have-in-account-name/15086/2 "2017-06-11T12:00:13Z")

</div>

At what point do you evaluate your use of email address as entity name 😛

---

<div class="post-metadata">

**Author:** ![mjb2000](https://forum.sambapos.com/user_avatar/forum.sambapos.com/mjb2000/32/29209_2.png) [@mjb2000](https://forum.sambapos.com/u/mjb2000)\
**Post date:** [June 11, 2017, 8:12pm UTC](https://forum.sambapos.com/t/cannot-have-in-account-name/15086/3 "2017-06-11T20:12:45Z")

</div>

I would rather just use a randomly created customer ID and allow my team to specify name and email address as customer fields… but I have asked that before I just shot-down.

Therefore email address is good enough as a unique ID, so I decided to use that for the customer name.

**The real danger here** is that if you have a customer account naming template containing something like `[NAME]` and the operator drops an @ in their (maliciously or by accident) then they can gain full access to the accounts screens.

---

<div class="post-metadata">

**Author:** ![JTRTech](https://forum.sambapos.com/user_avatar/forum.sambapos.com/jtrtech/32/21270_2.png) [@JTRTech](https://forum.sambapos.com/u/JTRTech)\
**Post date:** [June 11, 2017, 8:17pm UTC](https://forum.sambapos.com/t/cannot-have-in-account-name/15086/4 "2017-06-11T20:17:20Z")

</div>

> [@mjb2000](#):
>
> The real danger here is that if you have a customer account naming template containing something like [NAME] and the operator drops an @ in their (maliciously or by accident) then they can gain full access to the accounts screens.

Understand that bit, that is a bit of a glitch.

> [@mjb2000](#):
>
> I would rather just use a randomly created customer ID and allow my team to specify name and email address as customer fields… but I have asked that before I just shot-down.

Not sure about shot down, pretty sure I offered you a sugestion… If you create new entities using automation and [?prompts] like in my room booking setup which creates a booking entity rather than guest entity and it auto populates the entity name with a booking number generated using date and a random suffix.

Here was the topic where I showed my setup;

> [@Hotel Rooms (Entity?)](https://forum.sambapos.com/t/hotel-rooms-entity/9854/14):
>
> I did a sting of automation based on a custom entity screen; Had a room entity grid and then a booking grid which was a custom entity screen which didnt select the entity but start a command flow starting with feeding the room name as command value; (Had to scale to 60% even with my multiple virtical monitor screen setup LOL) [image] [image] [image] Will upload a video of the workflow in a minute

---

<div class="post-metadata">

**Author:** ![mjb2000](https://forum.sambapos.com/user_avatar/forum.sambapos.com/mjb2000/32/29209_2.png) [@mjb2000](https://forum.sambapos.com/u/mjb2000)\
**Post date:** [June 11, 2017, 8:24pm UTC](https://forum.sambapos.com/t/cannot-have-in-account-name/15086/5 "2017-06-11T20:24:01Z")

</div>

> [@JTRTech](#):
>
> Not sure about shot down

No, I wasn’t referring to that thread, I was referring to this one…

> [@List tickets by entity ID \[Custom reports\]](https://forum.sambapos.com/t/list-tickets-by-entity-id-custom-reports/14056/):
>
> I am trying to get my head around customer reports and report tags etc but I am struggling on what I guess is a rather basic issue… I have used… {REPORT ENTITY DETAILS:E.Id,E.Balance.sum:(ET=Customers):{0}::($2!=0):,} to return a list of Entity IDs for Customers who owe me money. With this list of Entity IDs I want to get a list of tickets belonging to these entities. I a really stuck. Using {REPORT TICKET DETAILS:T.Id,EN.Customers} I can retrieve the customer name for each ticket, but I ca…

In terms of using the prompts… I really want to keep things as close to the core functionality as I can, although at this point I have made so many changes I maybe should just go with your custom entity creation method.

---

<div class="post-metadata">

**Author:** ![sukasem](https://forum.sambapos.com/letter_avatar_proxy/v4/letter/s/b38774/32.png) [@sukasem](https://forum.sambapos.com/u/sukasem)\
**Post date:** [June 11, 2017, 8:25pm UTC](https://forum.sambapos.com/t/cannot-have-in-account-name/15086/6 "2017-06-11T20:25:31Z")

</div>

> [@mjb2000](#):
>
> I just shot-down.

I think you ask to use Name as primary field and can be the same Name. Most of us suggest phone number but you doesn’t like it.

> [@mjb2000](#):
>
> I would rather just use a randomly created customer ID

That is the way to go. Unique ID as primary field. Just create global program setting to store last ID.

EDIT: Hmm… maybe not that easy we can’t use {SETTING:} in the field.
