Is it possible to use a space between fields in a numbering scheme?
I have tried without luck, but wanted to see if there was a wildcard of sorts which allowed it.
Thanks,
Jeffrey K. Ries
Detroit, MI
Solved! Go to Solution.
Solved by Kenny. Go to Solution.
Hi,
Could you please help me to understand your exact requirement? Do you want the space in between some Text?
For example "Test #001"
In this case I used the following
Fixed Text "Test " - Test and then Space
Delimiter #
Auto Generated sequence.
Is this the one you wanted? Please let us know.
Please note that you cannot have the space as "Delimiter".
Hi Jeffrey,
Here is another work around for adding space between two fields, maybe it is what you want:
1. You can define a schema adding free text field with max length is 1 between two fields.
2. As using the schema, remove the default value of the free text and enter a space.
For example you need "Test 0001", you can define a schema like "Test?####", as applying the schema to file name, remember enter a space for the "?", then you can get the "Test 0001".
Hope it helps.
Thanks
Kenny
Ideally, it would be nice if vault would accept a space as a delimiter.
We have many people who will be expected to enter their own file names. Without automation some users enter a space while other opt for an underscore. This leads to poorly sorted files.
Since our file names are sequential the difference of a space vs. an underscore can throw off the sequence and lead users to use an incorrect or existing number. (I am aware that vault has the ability to handle the numbering for us, but we already have a keynoting system in place which does that for us)
Is there any option which does not rely on the user for the space?
Thanks,
Jeffrey K. Ries
...and to clarify, here is the file name I am trying to automate.
[Client Code] [Underscore] [Project Number] [Space] [File Number]
WIDG_110163 134
Client code = Predefined list
Underscre = delimiter
Project number = Free text
Space = ??????
File Number = Free text
Jeffrey K. Ries
Hi Jeffery,
Here is another way to do this: defining a Pre-defined list field with only codeword " " and set the codeword as default. Then you don't need enter for the space as applying.
Take your schema for example
Client code = Predefined list
Underscre = delimiter
Project number = Free text
Space = Predefined list (with the only codeword is " " and set it as default)
File Number = Free text
Hope it works.
Thanks for your suggestion (Ideally, it would be nice if vault would accept a space as a delimiter). I think, we will take it into account. 🙂
Thanks
Kenny
Thank you Kenny,
That is a good work-around, which I never thought to try.
...and thank you for considering adding it to the list of possible delimiters.
Jeff