-
Have you looked at the sample I attached? Can you tell me what isn't making sense to you in the sample or my other posts? Where are you stuck?
-
Yup, it does. I'm not sure what else to suggest - Are you using all 32 bit Office? That is, both InfoPath and your regular Office install are the same?
-
You can use the approach outlined here: https://docs.microsoft.com/en-us/archive/blogs/infopath/conditional-default-values
-
I just sent you an email via the forum.
-
Sure. Attach the form to a reply under the Options tab.
-
So - the issue is sizing. I added another person / group to your form, and took a look at the view files, and the only diff was your broken control was set to 16 px height and 16 px width. My not-broken control is 27 px height and 360 px width. Changing your "broken" person / group picker to the correct height and width displayed it ...
-
So - if I put a calculated value into group17, which is the base path for your mapping, and select Employee Type, the XPath is: ../../../../my:EmployeeType which is why I think the relative paths to your non-repeating data may not be correct. Here's a copy of your mapping with the non-repeating fields changed, perhaps you could give it a try.
-
And just to make sure I understand - when you say "not working properly" you mean the data isn't submitted to the list? That column is blank?
-
So your other higher level fields are submitting data to the list? Just Employee Type is not?
-
I already did make a suggestion on this. I usually add a field to the data source for form name, set it on submit (including the current date/time to ensure uniqueness) and then use that for the form name in my submit connection. I should add - the condition to set the form's name should be that it only gets set when blank. I've made this ...