Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[JustinChase]

A while ago, I created a new library field called "Event" because the stock field "Event" does not allow a list, and I wanted to be able to use a list for this field, so I renamed the non-plural name of Event to Events, so I could have/use Event for my purposes.

Well, I've worked around that issue and now I no longer need, nor want my custom field, so I've deleted it.

I then changed the non-plural name of the stock field back to Event, and MC automatically added (1) to the end of the field name.  I assume because it keeps a hidden list of names someplace and won't allow a duplicate name.

but, since I've deleted my field, this name should be available again.  I've restarted, but I cannot get the stock field non-plural name to just be Event.

Can this be done, or have I forever poisoned this with a rescinded action?

[Matt]

I can't reproduce the problem.  I created a field twice so I got (1) added to the name.  I deleted both.

Then I created again and it didn't add (1) to the name.

A field named "Events" will get created every run of the program.

[JustinChase]

It allowed me to successfully remove the (1) this time.  Not sure if it was a time thing, or if I did something else, but it is fine now.

In case you wanna try to re-create...

I changed the stock Events field to change the display name from Event to Events.

I created a new field called Event and made it a list field.

I used it for years.  I thought I'd removed any data in that field.

I deleted the Event field I created.

I changed the display name on Events to Event and it forced the (1) at the end.  i tried deleting the (1) several times, but it kept adding it back.

I restarted MC and the behavior remained the same.

I thought I'd restarted the computer, but perhaps I did not.

Now, after several reboots and restarts, it allowed me to remove the (1).

Sorry for the waste of your time.