Hi Jana
Just so I understand, you're creating a single article. Then you want to extend that to the same set of plants/storage locations?
If so, one idea would be to:
- create a reference list (or db table) with a Query control in the form to read in the set of plants/storage locations/etc. into a table in the form.
- Then use a rule to set the article number to the one generated. It will basically overwrite that field in all rows.
Hope that gives you an idea. If I missed it, please explain what I missed.
Best Regards,
Sigrid
------------------------------
Sigrid Kok
PSE | Winshuttle NA
------------------------------
Original Message:
Sent: 03-18-2022 08:07
From: Jana Kuschmierz
Subject: AW: Winshuttle Open Forum : Extending Materials on a loop
Hello Sigrid
I had a little break and now I'm working again in the repeating table "Plant Extending".
The Form works in this way:
1. MM01 – press Button and create article
2. Log Field write the created item number
3. The item number is extracted and entered in the field "Artikelnummer SAP"
4. The item number is transferred to the field "Artikelnummer" in the repeating table "plant extension"
There are 2 fields in the repeating table I want to fill in automatically:
Werk
Lagerort
On each field I have a rule that I should run the query with the correct values.
5. When I press the Button "Neues Element hinzufügen" it creates 5 rows. This is correct.
BUT I would like that the 5 rows with the correct values are still there WITHOUT press "Neues Element hinzufügen"
I cannot find out how can I create the repeating table automatically with 5 filled rows.
Many thanks for your help.
Freundliche Grüsse
Jana Kuschmierz
Leiterin Verkaufsinnendienst
Tel. direkt: +41 62 887 70 34
Mobil: +41 79 127 07 74
jana.kuschmierz@rigips.ch
_____________________________
Rigips AG
Gewerbepark – Hintermättlistrasse 1 – 5506 Mägenwil – Schweiz
Tel. +41 62 887 44 44 – www.rigips.ch
Es gelten die Allgemeinen Geschäftsbedingungen der Rigips AG, abrufbar unter rigips.ch/agb.
I'm glad it's working, Jana. The counts and rules are optional: I add a few fields to have a count for number of rows and number posted - you...
| | Re: Extending Materials on a loop | | | | | | I'm glad it's working, Jana.
The counts and rules are optional: - I add a few fields to have a count for number of rows and number posted - you have to create them. I use those fields to display the number of rows processed, but I also them in rules to hide the post button, for example when the number of rows = number of rows posted.
- I used the count field I created in a rule to ensure the query control doesn't run if my input gets rejected and I have to go back to the view. You might be able to use the plant field in your table in a rule instead - if it's blank run the query, otherwise don't.
example count
i used the plant field in the table to trigger the count rule
note it uses the field name, not the field value for count.
If you want a count of the number posted, use the logfield in the table and apply a rule something like this
it's another count function with the field name of the logfield. The last part 'Material'|'created' is a regular expression. What I have in there means if the logfield contains Material or created, then I know it's posted. You can use whatever regex you like. Here's the doc on the count function: docs.winshuttle.com/foundation-en-12-1-x-online-help/...
Hope this helps,
Sigrid
Again, all extra and optional.
------------------------------
Sigrid Kok
PSE | Winshuttle NA
------------------------------
| | | Reply to Group Online View Thread Recommend Forward Flag as Inappropriate | | | | |