-
They each have to be their own rule. So you would need individual rules.
-
The good news is that the field is being set as anticipated (see screenshot, which shows the value of the field in the XML file). So there must be a different issue. You could try removing the column from the promoted properties and re-adding it, or you could try just re-opening this form and see if the value shows up in the promoted field. You ...
-
sum(../d:SharePointListItem_RW/d:l8xb[../d:Title = current()/d:Title]) - note how my formula goes up to the repeating node to summarize - ../d:SharePointListItem_RW
-
Ok. This is good. How do I know, looking at the Hiboux 3 data connection, which one is available? All I see in the data connection are the fields displayed in this screenshot - I'm using Province & the repeating Value node to determine who to show. Where does availability come in?
-
Maybe try this one - I might have to set up a test on one of my sites to get the XPath right, however - I'm sort of guessing on the filter. :)
-
Well - the Hiboux data connection has the right names & Ids, right? And then the Hiboux 3 data connection is the one that joins the Hiboux data with the Province data?
-
Attach one of the filled out forms (saved after you made the rule change) to a reply - I want to make sure the field is in the schema
-
Oh, ick, I see what I did wrong there. I'll see if I can fix that - it will be later today. By changing the dropdown to use Hiboux3, the values group just has the ID for the items, not the names.
-
So when you test with a new form, does the Request Type show up in the file name? Because it looks like it is there too.
-
Looks right now - it looks like Request Type is promoted and also used in the file name. Since this rule is on the Submit Rules, all submit buttons in the form will set request type to AOP Evaluation and submit using the ECC Request library. What is the symptom that indicates this is "not working"? Is the request type not in the file ...