InfoPath Dev

I've spent way to much time researching this and trying different things, time to ask the experts! I have a cascading drop-down in my InfoPath form. Works perfectly except for one thing. If there is no option, the drop-down still shows but it is empty. I want to hide it if it is empty and I can't get it to work. See attachment for table ...

Where is the rule? Is it on the field bound to the textbox? And where is the field that you are storing the date? In the same repeating table? You can always attach your form or a sample under the options tab in a reply - This should not require any code. :)

Wonderful - have your users test & holler if you run into trouble. :)

Hi I have been attempting to timestamp a textbox in a repeating section control however it only works for the 1st repeating section What I am trying to achieve is each time a new user goes into the form and adds a repeating section to log an update it will timestamp their entry. Has anyone got any experience with this without using any ...

 So far it seems to be working. I won't fully know until tomorrow until I have users other than me try it.

 Great, glad you got it figured out. Sorry if the forum ate your formatting - we are running on an older version of Community Server that seems to work best with Internet Explorer. :)

 I'm sorry for the delay, for some reason your replies are ending up in the moderation queue. I had to add some additional SPAM controls after a recent attack and seem to be getting some false positives on moderation. So - if you are using IP 2013, that means you are using Visual Studio 2012? I think you may be following code samples for ...

 Hello! So I'm completely new to InfoPath so bare with me here. Not much of a hardcore coder or anything.  What I want to do is create a form on InfoPath that will ask for a name. Then I want the form to check outlook contacts for validation if the name exists. From there it can auto-populate the other field such as phone ...

 It does. Thank you. I'll give it a shot and let you know how it works out.

 Okay - so instead of using SharePoint groups for this, you'll have to add a SharePoint list to track who should have what permissions, unfortunately - and manually keep it updated. I'd probably have one column for the user & have that be a person / group type, so that you can make sure the user info in accurate - the AccountID ...