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

Question

Question

No Entry Specified with Search Repository>For Each Entry

Workflow
Updated June 14, 2017
asked on June 14, 2017 • Show version history

UPDATE: 

I updated the Retrieve Field Values to remove a couple, and now I don't receive the error "No Entry Specified," but instead get another error on the Routing Decision activity"

 

___________________________

 

I've been trying to re-route existing documents within various levels of folders by using the Search Repository and For Each Entry activities. The search results in 413 entries, but in attempting to retrieve field values from each entry, I get a "No Entry Specified" error and I can't figure out why since I get results from the search.

 

0 0

Answer

SELECTED ANSWER
replied on June 14, 2017

The conditions in Branch and Branch 4 still reference the starting entry.

0 0

Replies

replied on June 14, 2017

My first thought is that your "For Each Entry" activity is pointed at the "Starting Entry" or isn't specified. Is your "For Each Entry" activity setup like this:

Confirm that it is pointed at the entries returned from the "Search Repository" activity.

1 0
replied on June 14, 2017

This is what the For Each Entry is pointing at - there are no other options:

 

0 0
View 3 previous replies
replied on June 14, 2017

Thanks for confirming. I'll see if I can come up with any other ideas.

0 0
replied on June 14, 2017

My next question is, is your "Retrieve Field Values" activity pointing to the "Current Entry" of the "For Each Entry" activity?

1 0
replied on June 14, 2017

It's pointing to For Each Entry-Current Entry:

0 0
replied on June 14, 2017

Thanks for confirming again. In this case, I'm a little stumped. At this point, the last thing I can think to check is that your WF user has access to that section of the repository. Everything else looks like it's setup correctly.

0 0
replied on June 14, 2017

The user has the proper rights, I don't see any Access Denied errors.

0 0
replied on June 14, 2017

I'm sorry I don't have any other suggestions or ideas! Hopefully another Answers member will have a useful suggestion--I'd like to know what's going on with this myself.

0 0
replied on June 14, 2017

I updated the Retrieve Field Values to remove a couple, and now I don't receive the error, but instead get another error on the Routing Decision activity"

 

0 0
View 1 previous reply
replied on June 14, 2017

I'm guessing that before you didn't have the Retrieve Field Values activity published with the correct entry selection.

Now, it seems that your Routing Decision activity is referencing the starting entry in one of its conditions rather than the current entry from For Each Entry. Can you attach a screenshot of the conditions?

0 0
replied on June 14, 2017

I also updated the Retrieve Field Values to reference the Current Entry from the For Each Entry activity before I ran the updated version. Below is the current setup:

0 0
SELECTED ANSWER
replied on June 14, 2017

The conditions in Branch and Branch 4 still reference the starting entry.

0 0
replied on June 14, 2017

Thank you!! smiley

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

Sign in to reply to this post.

Details
Related Posts
Loading ...