Hello.
I have strange BPF's behaviour. In case when an entity form contains BPF, each update of any field contains next set of fields: "processid", "traversedpath", "stageid", "modifiedon", "modifiedby", "modifiedonbehalfby" + ID field. Also, update of the fields "processid", "traversedpath", "stageid" triggers the call of all WFs that are in current stage of the BPF.
This situation lead to the mess with BPF WFs. Has anyone encountered this situation?
Regards
*This post is locked for comments
Hi,
Similar issue is being reported. Please raise a ticket with Microsoft right now.
Might be a bug like you said
Maybe, I vaguely put it, but I see "processid" field in dirty fields in the situation when I just update an entity without changing stage of a BPF.
No, there is't active SLA.
Fields "processid", etc. are modified when you change the stage of the BPF.
Is there a SLA active on this entity?
I see that all updates are from only one user. Also, fields updated in one transaction. Moreover, it looks like I changed "processid", "traversedpath", "stageid" from the form, but i didn't.
I created the same situation for Case - entity without any custom changes. And reproduced the problem. I believe that it is Microsoft issue :(
Hi there,
Can you see in the Audit History if these updates are made by more than one person?
#1
André Arnaud de Cal...
292,516
Super User 2025 Season 1
#2
Martin Dráb
231,407
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
