InfoPath Dev

I have a document type that I believe Ernesto helped me set up. I am attempting to update the database connection string. The new connection string validates, but am unable to save the change because I am receiving a validation error. I do not recall how this document type was originally set up without the table having an identity column. ...

Hilary, I think you oversimplified your solution. If I create a new field and set its default value to that of the original "master" field then the new field is set to the ID value, not the display name of the lookup. For anyone else reading this thread, I can use a second field's default value as described above if I set the ...

Ernesto, The problem returned and a reboot of the SharePoint servers resolved it. I suspect it may return again. The forms are published via Central Administration as administrator approved form templates. Oddly, one out of five forms is not effected. The form not effected is submitting to DBXL, the three forms that case errors when rendering ...

Jim, I am seeing the user's ID in the Author column and domain\user ID in the CreatedBy and ModifiedBy. I will try granting the user specific permissions in DBXL and if that works then I will look to see if there is an issue with the AD group.

The form is admin deployed. The main (parent) form is mapped to SharePoint while the embedded (child) form is not. See attached.

Question for Ernesto, what sandbox are you speaking of? I'm not using a SharePoint sandboxed solution. Granting NT AUTHORITY\Authenticated Users permissions works. It's not ideal since it negates the entire security feature of permissions- if I have to grant everyone permission then why pretend there is security.

See attached.

I have InfoPath 2010 web forms that submits via qRules 4.2 to DBXL 2.6. I, as a DBXL administrator, can submit forms. Users are not able to submit forms. They receive the following error, where "author" is the user's account name: Action: SubmitToDbxl. Arguments: submit: SubmitDocumentToDBXL doctype: fundingForm ...

The issue appears to have involved DBXL not being able to connect to the database server. Complicating matters appears to have been some strange behavior with SharePoint involving caching/syncing settings and forms.

I have forms that use SharePoint lists as lookup tables. The forms write to DBXL which then writes to a form library on SharePoint and a SQL Server database. The forms written to SharePoint work fine, but the data written to SQL Server for fields using name/value pairs is the value and not the display name. How do I write the display name to SQL ...