You are viewing limited content. For full access, please sign in.

Question

Question

how to change existing template field values to upper case

asked on October 25, 2019 Show version history

I am trying to change existing field values (Student ID) to uppercase. Over time, people have added some values all lower case, some all uppercase, and some that are mixed. For consistency we want ALL the ids to be upper case.

I can search the repository for all the documents that I want, see below:

 

Normalize:
Connection Profiles:
• LBCC-Archives (vm-alb-lf.lbcc.linnbenton.edu; LBCC-Archives; listerf)

        Search Repository:
        Search Query:
                ({LF:Creator="listerf"} | {LF:Owner="listerf"}) & {LF:LOOKIN="LBCC-Archives\Student Services\Enrollment Services\Financial Aid"}
        If a search result is a shortcut, keep it as a shortcut
        Default
        Return: All results
        Additional Properties:
        Fields Options Properties:
        Sorting Properties:

        For Each Entry:
        Iterate through the entries in:
        (Search Repository::Output Entries)

                Assign Field Values:
                Entry: (For Each Entry::Current Entry)

 

In the Assign Field Values, how do I get the existing ID value, change it to uppercase, then save the new uppercase value ???

Some documents have different templates.

 - doc1 uses template1 that has field 1

 - doc2 uses template2 that has field 2

 - doc3 uses template3 that has field 3

Should I have a process for each template?

Or can one process update field1, field2, or field3 depending on which template the doc has?

 

Thank you

0 0

Replies

replied on October 25, 2019

You can create a single workflow but inside the For Each Entry, add a conditional decision with a branch for each template that you wish to process.  Each branch would have a if template equals condition.

0 0
replied on October 28, 2019

Okay so that fixes the template issue, How do I change the field(s) to uppercase? And as a side question, Is there a camel-case option?

 

Thanks,

Frank

0 0
replied on October 28, 2019 Show version history

Hi Frank,

You can use the Workflow Token Editor's "To Upper" function.

You can convert to Upper, Lower, or Title Case.

See example workflow below:

WorkflowTokenToUpperFunction.png
0 0
replied on October 28, 2019

replied on October 28, 2019

Hi Frank

Your Workflow can be fairly simple, and you don't have to pick a template, as you can just pick the field on it's own, which would make it easy of the Field in included in Multiple Templates.

In the retrieve option, in my example I'm using Customer Name, but there you would put your field

Then in the Assign Field Value you would do the same thing, but would right click on the field and open the Token Editor. From there under Functions choose "To Upper" so when the field is written back it will be changed to Upper Case

0 0
replied on October 28, 2019

pic0

 - my test folder

pic1

 - look in my folder for template "Financial Aid"
 - returns 4 entries >> correct

pic2

 - for each output entries for Search Repository

pic3

 - retreive "Financial Aid - SSN" field
 - for each "current" entry

pic4

 - edit field value
 - for each "current" entry

pic5

 - no change to repository

:(

Is there a time delay or should this change right away?

 

Thanks,
Frank

pic0.JPG
pic1.JPG
pic2.JPG
pic3.JPG
pic4.JPG
pic5.JPG
pic0.JPG (59.8 KB)
pic1.JPG (70.65 KB)
pic2.JPG (48.73 KB)
pic3.JPG (56.86 KB)
pic4.JPG (91 KB)
pic5.JPG (59.8 KB)
0 0
replied on October 28, 2019

Can you open one of those entries and view its metadata pane? The values shown in the column view could be cached.

0 0
replied on October 28, 2019 Show version history

The change would be immediate, but to Samuel's point, check the actual Metadata Pane

0 0
replied on October 28, 2019 Show version history

When you ran the workflow, were there any messages? You could add a Track Token Activity to see the Variables and how they react. Commonly used for troubleshooting.

0 0
replied on October 28, 2019 Show version history

Yes, I scanned in the files to the test folder myself and manually added the values to each field

pic6.JPG
img0.JPG
img1.JPG
img2.JPG
img3.JPG
img4.JPG
img5.JPG
img6.1.JPG
img6.2.JPG
img6.3.JPG
pic6.JPG (57.3 KB)
img0.JPG (68.12 KB)
img1.JPG (80 KB)
img2.JPG (60.18 KB)
img3.JPG (65.9 KB)
img4.JPG (56.09 KB)
img5.JPG (58.63 KB)
img6.1.JPG (127.2 KB)
img6.2.JPG (40.96 KB)
img6.3.JPG (40.6 KB)
0 0
replied on October 28, 2019

Workflow looks right, not sure why it's not working as expected. I expect it's something simple but can't put my finger on it. if you want to connect, drop your contact info

0 0
replied on October 28, 2019

Best time to connect is 9 AM to 4 PM PST
minus 12 PM - 1 PM for lunch
Monday - Friday

 

Frank Lister
MIS, CCNA R&S

Linn-Benton Community College
T-117
6500 Pacific Blvd. SW | Albany, OR 97321
Phone: 541-917-4839
www.linnbenton.edu

logo

0 0
replied on October 29, 2019

Today I started my computer and tried to run the workflow process and it worked!!

and it worked correctly

Is it because I restarted the program? Restarted my computer? Is there a delay?

 

Thanks for all your help,

Frank

0 0
replied on October 29, 2019

Well so much for that.

It worked in my test workflow

but does not work when I try to update a live folder

I even restarted the WL

I even renamed the WL

still nothing

 

 

0 0
replied on October 29, 2019

Okay, it looks like I wasn't "publishing" the changes

Changes published and...

it is taking forever

surprise

must be doing something ........

0 0
replied on October 29, 2019

How many documents did your search return in the live repository?

0 0
replied on September 12, 2024

I am having the same issue in my production and test environment. I published the workflow and ran it, and the desired field value did not update in the retrieved entries. 

 

When I try to track tokens for troubleshooting purposes, it does not create a token for assignfieldvalues_document title, only for the template_id, template_name

What was the solution?

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.