-
Can you check and see if this form behaves as anticipated? Save locally, right click and select design. Preview. On my Win10 InfoPath 2013 machine, this works as anticipated - however, I vaguely remember another thread about this that I'll see if I can find.
-
Maybe because I'm using equals here instead of contains - but try this sample form and see if this is what you mean. Save locally, right click, select design - the condition to hide rows that I added was simple - but let me know if you have to use contains in your scenario and I can see what that needs to look like.
-
It doesn't - let's try the Fiddler trace approach. You would need to have Fiddler installed on your machine & open while you publish - once publish fails, you can look at the list of the URLs in the left pane of Fiddler for the publish URL - it will likely be red, since publishing failed. Then you could look at the request & ...
-
I would try running Fiddler while publishing, finding the publish request / response & see if there is any better info there. Another place to look is your SharePoint ULS logs. Is your SharePoint server up-to-date on patches?
-
Put the TotalRequest field on the form, but don't format it, so you can see the actual value. Is it greater than or equal to 100000? Usually, I find that I have issues like this when the value of something isn't what I think it is....
-
For your fields that will be different for each record, drag the repeating group from the schema (you will need to show the advanced view in your data source task pane) onto the form - put all the fields you want to have with unique data in there. For the fields that will be the same, you can also drag the repeating group, and add the ...
-
When you create a connection to a SharePoint list in InfoPath 2010 and later, the data connection contains query fields. You can set the query field to the employee ID and then run the query to return just that employee. Query fields only use equivalence for comparison. So - you'd need to change the Employee Location List to not query when the ...
-
Is this using on prem SharePoint? Or online? If on prem, you could change that setting for InfoPath Forms Services. Or, you could set up your employee data so that you can leverage query fields to get back just the data you need, which is what I'd recommend. However, I see in your rules you are using contains to get the information for the ...
-
What do you want to change the background of? Can you attach a screenshot under the Options tab in a reply to show me?
-
Right now, the validation rule is "Type_of_Separation" is present - change that to "is blank" instead of "is present".