Cannot have @ in account name

[JTRTech]

@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?)

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; [image] [image] (Had to scale to 60% even with my multiple virtical monitor screen setup LOL) [image] [image] [image] [image] [image] [image] Will upload a video of the workflow in a minute