-
It looks like one of your added fields still does not match. The RFC_Go_Live.
You also need to run throught the data connection wizard on your main connection to clean up the data connection. That way it won't be expecting more fields than you have, this may have been the issue when you deleted them originally.
You can open a ...
-
InfoPaath documents (XML Files) always reference the published Template they were created from. This is embedded in the file.
You may want to check out the migration tool.http://www.qdabra.com/proddetail.asp?prod=QUploadDownload
-
Are you submitting to Access? You can have a autonumber field but you will not see the number until after you have submitted once.
You can create a table which is a list of numbers but the challenge is, if you have multiple form users, that you do not get duplicates.
-
Hi Stephanie.
I would look at what the source of the drop down data is. Is it coming from the repeating information? If so then a control within the repeating group would only see its parent, not the entire group be default. You may need to back up one level so that it can show all of it. Otherwsie look at an external source ...
-
I do not think there is any way around what you descirbe. Roles are not perfect. Have you consider using Active Directory instead? Then you can check group memberships specifically.
-
I am not sure your layout but typically you would use filter to get the date values from a particular row or the current() function to reference the current row.
It is probably one of these two.
If you need specific, live help you can purchase support credits here. http://www.qdabra.com/products_all.asp?cat=12
-
From the way it sounds I believe the issue is with SharePoint not with InfoPath.
There is a German language pack for SharePoint you might want to check on that.
-
Sharepoint is not preserving these characters. Do you have the appropriate language packs on the server and the clients?
This would probably be something to post on SharePoint forums or take to Microsoft.
-
That was the other option, conform SQL to the format you need. Often other people are using the SQL data already and that luxury of changing SQL columns is harder to come by.
It sounds like you either have a default setup or a rule that is populating these date fields.
Check the properties on the repeating table and check the ...
-
Are these promoted fields or the actual fields in the form get changed?
So if you cave it and reopen it do the values in the form change? I am guessing this is with promoted fields in the SharePoint view.