Mergeable Files List Truncated?

[mbrown]

Greetings,

We have a fairly large list of mergeable files, however there are a few more we want to add.

When we load up the admin tool, our list show's truncated mid file extension, it seems that our list has reached the maximum characters for the text box. If we add an additional extension in this list, and submit it, are we likely to lose the part of the list which we currently cannot see?

If so, is there some other way I can update this list?

Thanks for any help.

[Beth]

There isn't a way to make it larger at the moment. I can take a feature request though.

[mbrown]

There isn't a way to make it larger at the moment. I can take a feature request though.

Fair enough, a feature request is good idea. However, is there some other way I can handle this situation? I need to add more to the list whilst maintaining the current list, if this isn't possible via the Admin Tool UI, then I am looking for a work around, via the api or otherwise.

Any advice?

[Beth]

What version of Vault are you on?

Since you mentioned an admin tool, it sounds like an old version. The new version is capable of handling far more in the mergeable file list.

[mbrown]

We're using Vault 4.1.4

[Beth]

How many extensions are you trying to enter? I have been continuing to enter extensions and they get added in alphabetical order and haven't found a limit.

Also, if you click in the box and use the arrow key to move further right, do you see rest of the extensions then?

[mbrown]

We have about 40 items, the text box reads:

ascx; asmx; aspx; bas; build; c; cls; config; cpp; cs; css; demo; disco; frm; h; hpp; htm; html; inc; js; lab; mak; mst; odx; pl; prg; prod; qpr; rc; res; resx; sql; stage; strings; txt; vb; vbp; vbs; vct; xm

As you can see the last one is probably supposed to be xml (which we can merge), and then I'd image we have a few others past that, as I am pretty sure we can merge xsd and xslt files.

We tried using the arrow keys, however we weren't able to move past "xm".

I should clarify that we can continue adding extensions into this box, but we're concerned that when we submit the change we'll lose all the extensions past the "xm", whichever ones they might be.

If this field is stored as separate records in the database then it may not be an issue, but I was hoping to confirm this before we try it.

Thanks for the help so far.

[Beth]

Each entry in that field is stored separately in the database.

Are you placing semicolons in between each entry?

If you add an entry into the center of all the other entries, does more of the field get cut off?

[mbrown]

At this point I think I have enough information to experiment on my own.

I'll be sure to post any additional findings.

Thanks for you help.

[mbrown]

It seems that at some point we committed the truncated list (likely with the version 3 client we used to have), so we took the plunge and we've been able to add all of our file types and nothing is being truncated.

I'm not sure if this was a bug in version 3 (or earlier), or it was always user error, but this is now resolved for us.

Thanks for your help.

[Beth]

Thanks for the update.