-
I found that using this filter - [my:Total != 0 or my:PullID !=''] works just fine for my scenario.
-
It appears that it does not like the syntax. I get a "Failed to generate batch from mapping" error with the combined rule.
-
That what I'm talking about!!!! Thanks! Eventually, I won't be too quick to exhaust all my mental resources.
-
[quote user="Hilary Stoupa"]
Sounds like you are saying you want:
[my:Total != 0 and my:PullID = '']
So that you submit anything that has not been submitted (i.e., pull id is equal to blank) but has a total that is not equal to zero.
[/quote]
Actually, now looking at it, I think I need -
[my:Total != 0 or ...
-
Uhhhhhh. It's Monday again. ; ) Thanks. Sometimes it's the simple things.
-
OK, I thought it would exclude items with a total of 0, and that don't have an existing list ID. Both conditions together for one row of a repeating table. And yes, the PullID the ID I'm using for the Submit.
-
So shouldn't this work, if I am submitting a value of not zero the first time it is submitted ?
[my:Total != 0 and my:PullID != '']
Because it is not working. It won't submit anything.
I figured I could do it this way, because when an item is edited, and possibly zeroed out, it would still submit because the ...
-
Yes, but is there a workaround that you can think of? Is the ID set after the SubmitToSP command is run?
-
Basically to try to get around the insert workaround to copy table (I just don't want to do the insert, there's too many fields in my table to populate), I am trying to filter my submit in such a manner that it does not submit items that = 0, unless it exists in the list already. Therefor I tried to filter this way -
[my:Total ...
-
When does SubmitToSharePointList assign the ID? I was messing around with not submitting items if the ID is blank, but it looks like the ID is assigned to late in the process, so it wouldn't submit anything at all.