I wanted to create metadata fields with the same names as already used for our documents.  Since we have a title that is different from the filename I created a "Title" custom attribute.  This is the same name as one of the non-custom attributes and the DMX module crashed with no opportunity to repair from the web site admin.

Since we were just starting, we uninstalled and reinstalled DMX

This leads to 3 requests:

1. Before accepting a custom attribute name, check the exisiting attribute names (custom and non-custom) for duplicates

2. List the non-custom attribute names greyed out on the custom attribute pages so we know what names are taken.

3. Provide documentation on how to remove a custom attribute from the code page side so that DMX doesn't have to be removed to repair DMX if this happens.

Thanks

Let me know if anything is unclear.

Thanks Peter.

Hi there, have had a very similar problem occur twice this week, once after re-installing the module.

The custom attributes I had were 'Created' and 'Owner', but as these weren't in the core attributes, I think its some kind of timeout issue.

On both occasions I had left the machine for over 10 mins on the 'Core Metadata' entry page, come back, clicked 'Finish' and it crashed with the error. 

Any tips on fixing this without having to re-install would be most appreciated, I know Peter is away until next week.

thanks,

simon

Hi Peter, 

Yes I think I'm going to have to. You could probably do with publishing these potential conflicts as a list somewhere short term, and putting a validation routine in there long term I think though to save future problems.

Only drawback with the short term fix is obviously the display won't be quite as nice with the "My_" attached. Perhaps something like Custom Attribute = "#Owner" and  Display As = "Owner" would be better.

thanks,

Simon

Hi Peter, yes please - thats definitely a tad oriental to me, I come from an html/javascript background and I'm not very familiar with SQL or ASP I'm afraid.

Incidentally did you see my webdav issue over in the other forum, its very close to being fully working, but as they say - no cigar!

thanks peter