Automate

The issue i am having is when i create my repeating table and then map a script to it, I can either get the script to run through one line or no lines.  When i import the script i assign the Group name to the group that contains the RT.  if i check the "generate repeating section", the script does not process any lines of the RT.  I also notice that the "allow_run" field gets created in a separate group in the list of data elements.  if i don't check the box then i can get one line to process. 

Any help would be greatly appreciated. 

thanks

------------------------------
Jeff Linde | Data Solutions Engineer
Patterson Companies | [City] | (651) 994-2231
------------------------------

​I'm going to assume that you have a loop around the fields (in your transaction script) that map to the fields in the repeating table.  When looking at the mapping in composer, do you see where it is mapped to line1.<fieldname>?  Are all of those mappings correct? 
I find it is easier to create the transaction script and then import it in and let composer handle the mappings rather than create the repeating table and import/map it myself.  For some reason, when I map it myself things go awry.

------------------------------
Kim Grathen | Business Analyst
Kwik Trip, Inc.
------------------------------

​It has been a little while since I have been working with these, but I think this is what you need.

- In Form Data

• a group that has "_Input"
• a "Repeating_Content" group under that "_Input" group
• "_allowRun" under the repeating group
  
  

The "_allowRun" will either need to have a constant of TRUE or be on the form view, in the repeating table, where the transaction script/web service is run from.  It needs to be TRUE for the script to run that line.

The fun is how the groups are created.  It could be from a Query import, Transaction import, dragging a repeating table to the form, etc.  I think you can update the groups manually, but I cannot recall fully.

------------------------------
Scott Gorski
General Mills | Advanced Analyst, Master Data Management
------------------------------

Original Message:
Sent: 10-10-2018 14:27
From: Kim Grathen
Subject: Transaction script running through lines in repeating table

​I'm going to assume that you have a loop around the fields (in your transaction script) that map to the fields in the repeating table.  When looking at the mapping in composer, do you see where it is mapped to line1.<fieldname>?  Are all of those mappings correct?
I find it is easier to create the transaction script and then import it in and let composer handle the mappings rather than create the repeating table and import/map it myself.  For some reason, when I map it myself things go awry.

------------------------------
Kim Grathen | Business Analyst
Kwik Trip, Inc.
------------------------------

Hi Jeff

For repeating  tables/groups, you need all of your fields in the same Composer data model group.

So you can (a) create your own group and manually map the fields in it to your script, with all of them in the same group OR (b) let Composer generate the data model for you, creating the groups.  I believe this option was already recommended.

This is especially important with the repeating web service checkbox checked.  I always do option "b" for these, letting Composer generate the data model.

Hope that helps,
Sigrid

PS for line item updates, I have sometimes imported the transaction script, generating the data model, and then mapped the output of the query to return the line items directly to the repeating group of the transaction script.  Saves a lot of work.  But again, all of the fields in the repeating group are in the same group.

------------------------------
Sigrid Kok
PSE | Winshuttle North America
------------------------------

Thank you all for the suggestions.  i will give them a try.  Currently i am using the savedata BAPI and mapping it myself to a group that i have aready created.  I am setting the allowrun field to "true" via a button (the defaulting to true did not seem to work once the table was loaded from a query.  The allowrun is on the form and is being checked.  i will go back and validate that the groups are correct and that the allowrun is also in the same group.  I think that is my problem.

Thanks again for all the help.

------------------------------
Jeff Linde | Data Solutions Engineer
Patterson Companies | [City] | 6519942231
------------------------------

Original Message:
Sent: 10-16-2018 09:15
From: Sigrid Kok
Subject: Transaction script running through lines in repeating table

Hi Jeff

For repeating  tables/groups, you need all of your fields in the same Composer data model group.

So you can (a) create your own group and manually map the fields in it to your script, with all of them in the same group OR (b) let Composer generate the data model for you, creating the groups.  I believe this option was already recommended.

This is especially important with the repeating web service checkbox checked.  I always do option "b" for these, letting Composer generate the data model.

Hope that helps,
Sigrid

PS for line item updates, I have sometimes imported the transaction script, generating the data model, and then mapped the output of the query to return the line items directly to the repeating group of the transaction script.  Saves a lot of work.  But again, all of the fields in the repeating group are in the same group.

------------------------------
Sigrid Kok
PSE | Winshuttle North America
------------------------------

Thank you all again for your help.  I was able to get it working by importing the script and letting Winshuttle create the group.  i then drug the items from the Form Data tab into my repeating table. 

So thanks again.

------------------------------
Jeff Linde | Data Solutions Engineer
Patterson Companies | [City] | 6519942231
------------------------------

Original Message:
Sent: 10-18-2018 14:51
From: Jeff Linde
Subject: Transaction script running through lines in repeating table

Thank you all for the suggestions.  i will give them a try.  Currently i am using the savedata BAPI and mapping it myself to a group that i have aready created.  I am setting the allowrun field to "true" via a button (the defaulting to true did not seem to work once the table was loaded from a query.  The allowrun is on the form and is being checked.  i will go back and validate that the groups are correct and that the allowrun is also in the same group.  I think that is my problem.

Thanks again for all the help.

------------------------------
Jeff Linde | Data Solutions Engineer
Patterson Companies | [City] | 6519942231
------------------------------


Original Message:
Sent: 10-16-2018 09:15
From: Sigrid Kok
Subject: Transaction script running through lines in repeating table

Hi Jeff

For repeating  tables/groups, you need all of your fields in the same Composer data model group.

So you can (a) create your own group and manually map the fields in it to your script, with all of them in the same group OR (b) let Composer generate the data model for you, creating the groups.  I believe this option was already recommended.

This is especially important with the repeating web service checkbox checked.  I always do option "b" for these, letting Composer generate the data model.

Hope that helps,
Sigrid

PS for line item updates, I have sometimes imported the transaction script, generating the data model, and then mapped the output of the query to return the line items directly to the repeating group of the transaction script.  Saves a lot of work.  But again, all of the fields in the repeating group are in the same group.

------------------------------
Sigrid Kok
PSE | Winshuttle North America