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.

Status â›”Will not do
Categories Alloy Web
Created by James Gladwin
Created on Feb 26, 2025

Moving attributes from a design on to an interface

It is possible when creating a design to think that certain attributes only apply to that design, so it is not worth putting them on an interface. However further down the line, things can change and you regret that they aren't on an interface. There are also designs that were created prior to us being able to create interfaces, that would benefit from being tidied up.

I don't know if what I am asking is possible, but it would be good if we could retrospectively add attributes to an interface. Currently we would have to create a new attribute on an interface and add it to the design, then update that attribute for existing records, then hide the old attribute (or clear it and then delete). None of that looks good in the logs if we have court cases where we have to provide the history of an asset.

To go one step further, it would be useful if two attributes could be merged into one, but only if only one of them was populated. That would help tidy things up and make reporting easier.

I appreciate that if it is possible it would require thought as to the circumstances it could happen, but it would be really useful.

  • ADMIN RESPONSE
    May 15, 2025

    Hi James,

    Thanks for this one. Although this idea is completely understandable and in some instances be exceptionally useful, there are occurances where this will simply not be feasible. This would be ones where a similar attribute has been added to multiple designs and you would like them all to now be on a single attribute within an interface. In this case a manual move would still be required to ensure that all attributes are tidied up correctly.

    At this time it won't be taken forward to our development team.

    Thanks,

    Andy

  • Attach files