Custom Metadata problem

[jmdavid]

Hi,

I created 2 custom metadata for Categories named "My Date" and "My Value".
Now, when I try to edit a category, I get the following error: "Failed to update metadata".
When I want to create add a category, I get: "org.alfresco.service.namespace.NamespaceException: Namespace prefix rmc_My is not mapped to a namespace URI".

I tried to delete my custom metadata, but there is no Delete button!

Please help, thanks.

[jmdavid]

I also tried to edit the file "recordCustomModel.xml" directly in Alfresco Explorer; I made the file inline editable, removed my custom stuff and checked in with following error:
Unable to check in Content Node due to system error:09190018 Failed to validate model update - found non-incrementally updated ASPECT '{http://www.alfresco.org/model/rmcustom/1.0}customRecordCategoryProperties'

[norgan]

try renaming your fields so my-date or somtheing like that.

[jmdavid]

Thanks for answer but it doesn't work.  The label (title) is changed but not the name itself:

<aspect name="rmc:customRecordCategoryProperties">
            <title>Properties for DOD5015 Custom Record Category</title>
            <properties>
                <property name="rmc:My_Date">
                    <title>testdate</title>
                    <type>d:date</type>
                    <mandatory>false</mandatory>
                    <index enabled="true">
                        <atomic>true</atomic>
                        <tokenised>FALSE</tokenised>
                    </index>
                </property>
                <property name="rmc:My_Value">
                    <title>testvalue</title>
                    <type>d:text</type>
                    <mandatory>false</mandatory>
                    <index enabled="true">
                        <atomic>true</atomic>
                        <tokenised>FALSE</tokenised>
                    </index>
                    <constraints>
                        <constraint ref="rmc:5be5476a-71dc-4f23-8f59-c97a8b79f854"/>
                    </constraints>
                </property>
            </properties>
            <associations/>
            <overrides/>
            <mandatory-aspects/>
        </aspect>

Again, when I try to edit this file by hand and check-in, I get:
Unable to check in Content Node due to system error:09210003 Failed to validate model update - found non-incrementally updated ASPECT '{http://www.alfresco.org/model/rmcustom/1.0}customRecordCategoryProperties'

I read those threads:
http://forums.alfresco.com/en/viewtopic.php?f=7&t=16599
https://issues.alfresco.com/jira/browse/ALFCOM-3264

Seems that there is no solution.  Should I reinstall?  Very bad, not reliable for production yet.

[norgan]

you must not use the "_" character, that is used for masking the ":" character in the workflow variablespace. MAybe thats it

[apurcel]

Alas - I made the same mistake - entered a space in the meta data name - but even if I remove the space, the error message appears, and an underscore remains.

If editing the xml doesn't work - is reinstalling the only way to fix it?

[jmdavid]

Yes, I had to reinstall because once you created the custom metadata, there is no way to delete it, even when editing the XML file by hand (!!!).

[norgan]

That is not quite correct. You cannot remove the model until all content of that type is deleted and cleared from the database. You could also write a script to spider through all content and change the contenttype.

Norgan

[ebremer]

I had done the same thing, use a space in the custom metadata field naming within the records management interface and it started giving me errors.  Flushed the whole installation to clear it (I had not uploaded content yet, so it wasn't a big deal).  What I would like to know, is the space character is custom metadata fields actually an illegal?  And, if so, why does the GUI in RM even allow an illegal character in the first place?  - Erich

[dalequalls]

Any possibility of modifying the database directly?  Any idea on which table these are stored in?

I too put spaces in the custom metadata field name and now can't add any folders…

As far as for how deletions should work, I think a forced report generation should be done showing the affected records along with the audit info on who removed the custom field.  This data should all be stored in the audit tables or some type of a backup table so it can be restored in the event of a malicious or accidental deletion by an admin.

Just my 2 cents worth.

Thx!