Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Integration / Customization
IPA/ProcessFlow
PF and record counts
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Saef
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
5226
People Online:
Visitors:
315
Members:
0
Total:
315
Online Now:
New Topics
User Group Announcements
Carolina User Group Meeting
12/20/2024 3:15 PM
Date & Time: February 6, 2025, 8:30am - 4:00pm
S3 Systems Administration
ADFS certificate - new cert
12/3/2024 9:38 PM
The certificates on the windows boxes expired and
Lawson S3 HR/Payroll/Benefits
Post Tax Benefit Plan Table
11/14/2024 9:16 PM
Hi, totally new to Laswon. I have a repor
Lawson S3 Procurement
ED501 Error: Map 850 not supported by /law/c15vda/lawson/test10/edi/bin/laws_out_91
11/12/2024 3:47 PM
Tried runnning ED501 and getting the atathced erro
Lawson S3 HR/Payroll/Benefits
Error
11/6/2024 9:54 PM
When I try to enroll a retiree in 72.1 health plan
Infor ERP (Syteline)
Syteline: New Data Maintenance Wizard (Error) Need help
11/1/2024 4:24 PM
Hi, I need help with an error on syteline while us
Dealing with Lawson / Infor
Implementing Lawson v10 with Cerner Surginet, Case Cart Picking, and Quick Adds for the OR
10/29/2024 4:20 PM
Hi Everyone, I am wondering if there is any org
Lawson S3 HR/Payroll/Benefits
Canada Tax Calculation (Federal and Provincial) Issue
10/23/2024 5:00 AM
Initially, we had problem with CPP2 calculation is
Lawson S3 HR/Payroll/Benefits
CA Section 125 401k Plan
10/22/2024 10:13 PM
Does anyone have any recommendations on how to fac
S3 Systems Administration
Running AC120 deleted records from ACMASTER table
10/22/2024 3:40 PM
We recently ran the AC120 as normal and somehow it
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3291
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1372
Roger French
1315
mark.cook
1244
Forums
Filtered Topics
Unanswered
Unresolved
Announcements
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Integration / Customization
IPA/ProcessFlow
PF and record counts
Please
login
to post a reply.
9 Replies
0
Subscribed to this topic
52 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
Laura J
Basic Member
Posts: 4
7/26/2013 2:08 AM
Hello, I have created my first PF to capture assets from the AMASSET table and dispose the asset if a condition is met. I added an email message to include the asset number disposed. I would also like to build into my email message the number of transactions processed. I am using xxxxxx_RECORC_COUNT but it always returns 0 not the actual number processed. Any suggestions would be greatly appreciated on how to return the actual record count of transactions processed.
Tags:
PF
,
record_count
David Williams
Veteran Member
Posts: 1127
7/26/2013 10:21 AM
Are you trying to capture the number of records from the query? Are you capturing this count after the query has processed or within the query loop? I'm pretty sure you have to capture the count after the query loop and not within it.
Tags:
PF
,
record_count
David Williams
Veteran Member
Posts: 1127
7/26/2013 10:23 AM
And just to be sure, you are referencing it as xxxxxx_RECORD_COUNT - I figured you had a typo but just wanted to be sure.
Tags:
PF
,
record_count
Kyle Jorgensen
Veteran Member
Posts: 122
7/26/2013 11:56 AM
Also, be sure the "xxxxxx" in xxxxxx_RECORD_COUNT is the node's ID, not the node's name.
Tags:
PF
,
record_count
Laura J
Basic Member
Posts: 4
7/26/2013 12:36 PM
Hi, thank you for the quick responses! I am trying to capture the count after the initial query. After my query I am assigning a variable to the asset field. What type of node should be used to capture the record count?
Tags:
PF
,
record_count
David Williams
Veteran Member
Posts: 1127
7/26/2013 12:49 PM
If you need to retain the data returned from a query within your flow, you should define a variable in the Start node and then assign the query results, including record count, in an Assign node right away. The results of a query are non-persistant, meaning they can get lost within the flow after, for example, a Branch or a UserAction.
If you need to reference the Query_RECORD_COUNT within an email, you are better off to assign that to a variable right after the query is run.
Tags:
PF
,
record_count
Laura J
Basic Member
Posts: 4
7/26/2013 3:41 PM
Thank you, that was helpful. I added the Query_Record_Count to the Assign and I am receiving the record count but it is now only processing the last asset found in the query.
For example, Query finds 3 assets to modify. The Assign Variables are Asset_ID and Count
Branch Asset_ID.length>0 perform Transaction then message builder with Asset_ID and Count
Email message contains the last asset identified in the query and the only asset transaction processed is also for the last asset found and Email message contains Count = 3
What else could I be missing?
Tags:
PF
,
record_count
Bob Canham
Veteran Member
Posts: 217
7/26/2013 3:52 PM
If your query is returning multiple results and you need to action in each one, then you need to do the transaction node inbetween the query node and its return node. Then the transaction will happen for each queried record. You would also include your message builder to add the asset information. Then when the query loop is complete, you can use the Query_RECORD_COUNT and the message builder in an email to send a summary.
Tags:
PF
,
record_count
Laura J
Basic Member
Posts: 4
7/26/2013 4:29 PM
Thank you all for your suggestions. With my lack of knowledge and training on PF's I'm just not getting it so I am moving on! Thanks again!
Tags:
PF
,
record_count
Shane Jones
Veteran Member
Posts: 460
7/27/2013 1:16 PM
Laura,
Send me your flow and i will structure it so you can visualize how it would work. (don't want you to give up)...
Tags:
PF
,
record_count
Please
login
to post a reply.