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

Question

Question

Updating Word Document

asked on July 16, 2019

Hello,

I am trying to use the Update Word Document Activity in Workflow.  I have read through the White Paper, and followed a few responses to questions about this activity on Answers, however I cannot seem to get his activity to work. 

I am searching the repository based on Entry ID for a word file I created, with a field added, then attempting to update the field.  My preference is to simply overwrite the existing Word doc when the workflow finishes, but am able get neither the update existing nor the create new to work.

I cannot see what I am missing for this activity to work properly.

Any help is appreciated.

Thank you,

Darren

0 0

Answer

SELECTED ANSWER
replied on July 16, 2019 Show version history

True, but for troubleshooting purposes you can toggle over to Server Attachment real quick and upload your test doc as an attachment (or duplicate your activity) so you can see if Workflow will actually recognize the merge field you made. 

Try removing those field formatting pieces from the field name--we generally just use the actual text, i.e., MyTestField instead of «MyTestField».

1 0

Replies

replied on July 16, 2019

If the goal is to update the file in place, why not just use Attach Electronic Document on your search result? Just to double-check, your Attach Electronic Document activity is using the result file from Update Word Document and not the one from Download Electronic Document, right?

For the record, if you already have the entry ID, Find Entry is more efficient than Search Repository.

1 0
replied on July 16, 2019

Hi Miruna,

Adjusting the workflow as you suggested has yielded the same results

 

RE: Find Entry vs Search Rep., as this workflow grows, I've intentionally kept it very simple until i get the update word doc activity. As this grows into I don't expect to have the Entry ID to start with.  I expect I'll needed to use the search activity so I just started with that from the get go.

 

0 0
replied on July 16, 2019

Are you typing in the field name? It's not supposed to have the angle brackets in it.

1 0
replied on July 16, 2019

That was my issue. 

Thank you for your help.

0 0
replied on July 16, 2019

Try switching your create entry and attach electronic document.  In the workflows I have the attach electronic document always follows update word document.

 

As well instead of create entry would it be possible to invoke a workflow that you use for the ingestion of documents so it follows the same process?

0 0
replied on July 16, 2019

Hi Bill,

Switching the create entry and attach electronic document in the flow causes an error, as the document I am looking to attach needs an entry to attach to.

Moving the Create Entry to before the UWD, so the Attach Electronic Document activity runs directly after the UWD activity yields the same results described above.

My goal in this instance is to update an existing word document in the repository.  This workflow is designed as more of a proof of concept/Test for Users to show them things that LF can do.  In the pictured example above I am creating a new doc after update, but preference is to simply update the existing word doc without creating a new file.  However, I have been unable to get the update existing or create new options to work. 

 

Thanks,

Darren

0 0
replied on July 16, 2019

Hey Darren,

You're correct that you need to keep your Create Entry activity first. One thing that looks a little off to me is your Field Merge setting itself. Can you take a screenshot of your modification? 

For troubleshooting purposes, I'd recommend clicking the link that says "Import field names from document" in order to see what Workflow thinks is in your document. Use the field name that it pulls and map a value to it instead of manually entering in your merge field in the Field Name column and see what happens.

1 0
replied on July 16, 2019

Hi Anita,

In a search for a solution to my issue I came across a post (once i find it again I will link here) which explained that because I am finding a document withing the repository and not from the server, I cannot use the  Import field names from document. 

Screen shot of modification below

0 0
SELECTED ANSWER
replied on July 16, 2019 Show version history

True, but for troubleshooting purposes you can toggle over to Server Attachment real quick and upload your test doc as an attachment (or duplicate your activity) so you can see if Workflow will actually recognize the merge field you made. 

Try removing those field formatting pieces from the field name--we generally just use the actual text, i.e., MyTestField instead of «MyTestField».

1 0
replied on July 16, 2019

That has done the trick, removing the field formatting pieces from the field name solved my issue.

I could have sworn I tried that earlier before posting to no avail, however I likely had something else amiss at that time as well.

Thank you,

Darren

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

Sign in to reply to this post.