Question for the gurus: I'm trying to transition w...
# suiteflow
a
Question for the gurus: I'm trying to transition within an approval workflow to a separate state, if the vendor bill is a duplicate (same document number as another vendor bill for the same vendor). I set up a saved search and put it as the condition of the first transition out of the state on after submit, however it is being evaluated to false and I can't figure out why.
Standard Criteria is
type is bill
,
mainline is true
Summary Criteria is
Count of internalid is greater than 1
Results are Document Number (Group). Name (Group), and Internal ID (Count)
k
You probably need to script the value and make it a stored value field.
Your statement isn't true until the record is saved - and your transition wouldn't get triggered.
a
that's fine - i've done other summary searches in workflows that execute on after submit and they work fine
k
Also- what happens if you get same vendor bill number from more than 1 vendor. It's not a true duplicate at that point
a
the SS groups by vendor and document number
k
I've never used a summary search successfully in a saved search workflow status - it triggers incorrectly for me.
a
yeah they definitely work but something about this one doesn't for some reason
n
how can
internalid
count be greater than 1 as each bill will have a unique internal id. wouldn't your summary criteria be looking to count document numbers?
a
document numbers will be the same @Netsuite Tragic, meaning that internal IDs would be different - so if there is a count of internal IDs that is greater than one for a given common document number and vendor, then we know there is a duplicate
we aren't grouping by internal ID, keep in mind
anyway i abandoned this; i don't have any proof or documentation but i think what is happening is that the WF, when evaluating the SS results, is adding a filter of internal Id = (current record), meaning that the counting of other transactions won't work since they wouldn't be selected as part of the results for the eval
which i guess makes sense; i'll just add an add'l lookup in celigo to handle the dupe detection
n
got it, must read closer,
a
no worries, it's kind of tough to think through it, especially without the saved search in front of you as a visual