Skip to Main Content
Alloy Ideas Portal

Welcome to the Alloy Ideas Portal đź‘‹ Here, you'll be able to browse improvement ideas raised by our community, vote on ideas you agree with or even raise your own ideas. We review all ideas raised and we endeavour to respond to all raised ideas.

Any ideas submitted will be immediately visible on the portal for others to vote on, please do not include anything in your ideas you do not wish to be shared with others.

ADD A NEW IDEA

All ideas

Showing 17

Unique username within your own organisation

Currently the uniqueness of a username is run against all of Yotta's customers. A username: xyz1 is created by Organisation A. That username can't be created by Organisation B. This potentially can send a customer into an endless loop if the usern...
Guest about 2 years ago in Alloy Web 0 Will not implement

API access to set up computations

It would be really good if it could be set up so that we have controlled access to an area where we could configure computations without needing to request them from Yotta.
James Gladwin about 2 years ago in Alloy Web 0 Will not implement

Browser ZOOM level

When using Edge or Chrome, quite often to see what I need to in full, I have to zoom into a level of 67%. For example, on a query, If I zoom at 75% I lose the AQS Builder icon. When I zoom at 67% it becomes available again. However, I do not want ...
Guest about 2 years ago in Alloy Web 0 Will not implement

More options for file extensions when creating reports

When creating reports there are currently only 2 options for file extensions (*.pdf or *.csv). It would be helpful to have more options, in particular *.asc. An example of why this is required is the Street Lighting energy extract report. Our en...
Guest about 2 years ago in Alloy Web 0 Will not implement

Ability to change the order of attributes when bulk editing

Ability to change the order of attributes (ideally to follow a styling rule) when bulk editing. An example of where this would help is bulk issuing jobs as currently users have to scroll down to the bottom a long list of attributes to assign the T...
Guest over 2 years ago in Alloy Web 0 Will not implement

Geometry format in Data Explorer inconsistent with API

Items retrieved via API have geometry in GeoJSON format. Items exported from Data Explorer have geometry in WKT. Therefore the initial seeding of data in another system requires geometry to be converted which requires the use of another tool and i...
David Shepherd over 2 years ago in Alloy Web 0 Will not implement

Inform of signal strength before SYNC

It would be really useful if ALLOY had a way of determining if a SYNC would be successful before attempting it and if not (for example due to Poor Signal), inform the user and ask if they wish to continue
Guest over 2 years ago in Alloy Mobile 1 Will not implement