Workflow being fired twice from field update

(0) Share

Report

Posted on by djamr

I have a piece of javascript that fires on an event. Along with checking for certain fields to be completed it sets a custom field (option set) to a value indicating what the current stage is.

For this example the supervisor has submitted the report to the manager for review. Looking at the audit history I see this.

9/23 6:22	Update	Submitted to Manager	Submitted to Manager
9/23 6:22	Update	Pending Submission	Submitted to Manager

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (2)

Bruno Lucas 5,421 on at

Like (0)

Report
Copy link

Link copied!

which event is triggering this script? could the function also be running onload whenits set to initially run on save?

you can check the dependencies over that option set that gets updated

if you find something like a workflow, you can check this workflow and its dependencies to see if it is not recursive (calling back another process)

Was this reply helpful? Yes No
Verified answer

Aileen Gusni 44,524 on at

Like (0)

Report
Copy link

Link copied!

Hi David,

Did you use any force save function in your code?

Was this reply helpful? Yes No
Verified answer

Hosk on at

Like (0)

Report
Copy link

Link copied!

You should check to see if you have any javascript/workflows/plugins/business rules which are firing off the change of that field.

javascript save could happen onchange, onload, or onsave.

The javascript could save the form and then an onload/onsave adjust it again

Was this reply helpful? Yes No
NatrajY 3,040 on at

Like (0)

Report
Copy link

Link copied!

What rollup are you on? 6.1.1 (SP1 UR1) fixes issue where duplicate records are created when save is pressed mutiple times. If you have not installed SP1, this was fixed in UR3.

Relevent line from 6.1.1 release notes

"Duplicate records created if Save or Save and Close is pressed multiple times"

support.microsoft.com/.../2953252

EDIT: Didn't realise you said update and not create. Ignore this post.

Was this reply helpful? Yes No
djamr 5 on at

Like (0)

Report
Copy link

Link copied!

TGhanks for the suggestion, I didn't think about this approach. It is not the cause, but a great thing to know.

Was this reply helpful? Yes No
Suggested answer

djamr 5 on at

Like (1)

Report
Copy link

Link copied!

Hi Aileen, kinda.

I got pulled away on something and just got back to this last night. In my code I'm issuing a .save() and the a .close(). Looks like the save and close are both firing the save and even if the value has not changed it is being marked as a save a triggering the workflow. I removed the .save() and happiness is once again achieved.

Was this reply helpful? Yes No
djamr 5 on at

Like (0)

Report
Copy link

Link copied!

Seems like this might be related to one of the fixes in SP1 UR1.

Was this reply helpful? Yes No
Aileen Gusni 44,524 on at

Like (0)

Report
Copy link

Link copied!

Hi David,

It happened also in our development before, because we had code that fires force save submission, and then we see the audit history, got same time, but two submission.

Was this reply helpful? Yes No