cancel
Showing results for 
Search instead for 
Did you mean: 

How to use the for-each and conditional atoms to update a Business Partner?

Former Member
0 Kudos

Again, I apologize if this is simplistic, but I've recently been trying to learn quite a bit about the various atoms we can use in processing steps.  I've been successful in entering in a single call to a B1 atom, but I was curious about how to use conditional processing and for each processing atoms to potentially make multiple calls.  I have set up a processing flow as follows in B1iF

I have a single SQL call that starts everything and pulls data very simply with a SELECT CUSTOMER_ID, CUSTOMER_NAME FROM ORDERS.    I am trying to fill in the CardCode and CardName fields in B1 using this SQL call and hope to do it with the B1 Object in the middle of the for-each atom.  I could have up to 200 Business partners pulled from my SQL call. 

I have tried adding a path variable like /* to the path atom to allow the SQL call's data to reach the for-each atom.  When I reach the for each atom, I try processing the data for each row, so I enter in an xpath value of /vpf:Msg/vpf:Body/vpf:Payload[./@Role='C' and ./@id='atom1']/jdbc:ResultSet/jdbc:Row But the moment I try to debug this to see what message is coming off the for-each atom into the xForm atom I receive a "run could not be triggered" error.    The moment I remove the xForm and B1 Object atoms, the scenario step debugs without issue.

Would anyone have an idea of what's happening that they could share?  Can we not use B1 object calls in the middle of a for-each statement?  Am I missing something in the xpath I am using in the path or the for-each variables?  I am at a loss, even after reading the integration framework's documentation. 

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

My main problem here was having too many records I was potentially calling while debugging.  I had an SQL call atom that was bringing in 200 records and trying to then debug it.  Once I restricted the SQL call to bringing in 5 test records, I no longer received a "failed to run" error when debugging.

Answers (0)