Home → General Feedback →

Reordering custom metadata fields

• Edit

jolamar

25 Apr, 2013 02:05 PM

Before we upgraded to 7.2.2 we used to be able to enter in the XML configuration in custom metadata fields. The 7.2 release notes say that you've done away with this and replaced it with a click interface. http://www.hannonhill.com/kb/Release-Notes/7.2/index.html#easier-dy... Is it possible to either add the XML configuration in addition to the point/click or have a way to reorder the fields? For example, we have dozens of checkboxes that we want to organize alphabetically, but if we add something that starts with an "a" then we have to move each field down one at a time. It would be best if we could reorder the fields. I've included a screenshot to demonstrate the issue (The "a" field needs to be on top).

Another related question... if I add a field to a checkbox, and then go to the page and check that field, then go back and change the field name the value of the checkbox is lost. For example, I add a field called "cascadeserver" and then go to the page and select "cascadeserver". But I decide I want it to be "Cascade Server" so I go to the metadata set and change the name. When I go back to the page I see "Cascade Server" but it's not checked anymore. FYI, if I change it back to "cascadeserver" the check value is revived. We'd highly value the ability to change the name and retain the checkbox value. Is this a bug or should I submit this to the idea exchange?

Thank you,
Josh LaMar
Indiana University

• checkbox-metadata-field.PNG 20.8 KB

1. Support Staff 1 Posted by Tim on 25 Apr, 2013 05:30 PM

   

   Hi Josh,

   With respect to the new dynamic Metadata Field configuration feature you mentioned, we did away with the ability to modify the XML configuration. You aren't the first person I've heard requesting for the 'old' functionality to still be available (in addition to the new functionality) and I can certainly see your use case as being something that will crop up for others as well. Do you mind adding this to the Idea Exchange as a new idea? Please be sure to include the use case you've described here as well. It will certainly have my vote.

   As for the Metadata fields not retaining their values when the name is changed - this is just due to the way in which those values are stored in the database. There is a similar idea on our Idea Exchange with respect to Data Definitions as they act in a similar manner. Can you also add a new idea for Dynamic Metadata fields to retain their values when their names are modified? This will allow others to vote/comment on the issue.

   Thanks!

   • Edit

2. 2 Posted by jolamar on 25 Apr, 2013 08:34 PM

   

   Thanks Tim - I posted the idea at http://ideas.hannonhill.com/forums/52559-cascade-ideas/suggestions/... and voted on the other idea you linked to. This discussion can be closed now.

   • Edit

3. Support Staff 3 Posted by Tim on 25 Apr, 2013 08:40 PM

   

   Thanks Josh! We definitely appreciate your feedback. Have a great one.

   • Edit

4. Tim closed this discussion on 25 Apr, 2013 08:40 PM.