-
Yup, you are right - I mistyped those! So the easy way to find out how InfoPath stores data is to add a date time control to a form, fill it out, and open the saved XML with a text editor. I'll see if I can help w/ your other question.
-
Ah, I see - your schema is quite a bit different than mine. I'll try to set up something similar later today or tomorrow & let you know if I find a way to do this. :)
-
So - yeah, that seems weird. Your form seems right. You might want to try adjusting postback on the textbox where you are entering the data, see if that fixes it.
-
I don't understand why you formatted your date time to use a slash when you need to use the dash, as per all my earlier posts. Or why you are using a different format than what I suggested. As I've said, you need to format in a date time format that XML uses, which is yyyy-MM-ddTHH:mm:ss
Edited to add a sample date time - using ...
-
This seems to work as anticipated to me - see attached sample.
-
Take a look at the conditional formatting on the section - I'm just checking if the ID of the Vendor matches the selected Vendor. I made a modification to the new section in this sample - one thing that might also help while trying to work out the formatting is to change the conditions from hiding to just highlighting with a color.
-
Could you attach your latest template to a reply so I can take a look? :)
-
Add a calculated value control outside of any of the existing repeating sections on your form and set the value to:
sum(dfs:dataFields/my:SharePointListItem_RW/my:GJ2021Q1APV)
For example. Basically, you want to be outside of all the repeating sections so that when you create the "sum" formula, the XPath will include all ...
-
Answering question 4 now - I think you'll need to query the main data source to get all the related tasks.... so, hopefully title is unique (or some combination of the parent data is unique? Maybe you'll need to add an identifier of some kind that you use for everything submitted together?) You'll see in your main data source that ...
-
Whoops, I was item 2 here - I think I'd start with a formatting rule on the parent section to hide it, using the expression: count(preceding-sibling::my:SharePointListItem_RW) > 0