-
Ok - and right now you have the values for the first two dropdowns stored in the main data source of your form. Is that a design preference on your part? Or would an XML file in the form also be ok?
-
So - what you need help with is populating Enclosure Size? Do you want that to be a dropdown too? Or should it just be set based on the other selections?
-
Can you attach your form in a reply under the options tab? I can give you a hand with the filter.
-
If this is the main data source (i.e. the form is bound to the list), I don't think you'll be able to just submit a single row. It seems like you might be able to do this with some complex logic - just kind of brainstorming here, but I'd have my initial query and displayed rows bound to a secondary data connection to the same ...
-
So - the field the user enters data into - what is the data type? Is it a date field?
-
Hi - still having an issue with this?
-
Oh, great, glad you got it. Yeah, using translate is the only way to do this, unfortunately.
-
Ok, so submitting just re-submits the same XML file? The workflow runs on the same library the form submits to? I'd try recreating the workflow and see if you can repro it - because the created by field (if you are using the built in library field in your workflow) is going to be static in a list or library.
-
I removed a rule on your button, then added one to clear fields so you could pick a letter then pick another one. :)
Also, I think I have the filters backwards here:
xdXDocument:GetDOM("Teams_roster")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW[d:Dept = XPATH TO YOUR DEPT ...
-
Hey smarty pants, that's a great idea! :)