InfoPath Dev

Hi, I'm sorry this caused an issue for you. Just to clarify, DBXL will detect the doctypename in most cases. There are some (less common) scenarios, like this one, that do require declaring the doctypename. Can you tell us more about your scenario so that we may document it? Does your form have code? What version of InfoPath are you using? Any ...

When the form is submitted from the Sharepoint form library, does it show up in the Documents tab in DAT? If yes, do you get any errors when you click Reshred All in the Documents tab? Could you also attach a screenshot of the Database mapping tab in DAT? If you see any errors in the Qdabra eventvwr log, please post them. Thanks!

Hi, and welcome to the Qdabra world. I would suggest you walk thru our Getting Started guide: http://www.infopathdev.com/files/folders/core_documents/entry33862.aspx In it you'll find the basics: creating the submit connection, creating a doctype, configuring a SQL mapping, etc. Until issue 1 is solved, issue 2 cannot be addressed. If you ...

I can't find a previous instance of this situation, unfortunately. If you set the form library to open the form in InfoPath (not the browser) does the error reproduce? The other thing we should check is the submit data connection in your form. Would it be possible to attach a stripped down version of your XSN? I would just need to see the ...

Could you attach a screenshot or the text of the error message? Also, please check if eventvwr has recorded any additional information. One way to debug with IPFS is to change the form library settings to open the form in InfoPath. When the error is reproducible in InfoPath, we usually get a better error message. The IPFS error messages are ...

Hi Tobias, Looks like the problem is that the source table has a blank description. I tested by adding a description and the command works. Do you expect to have many blank values in your secondary data source?

Hi Tobias, Your main data source still contains a repeating group instead of a repeating field, so there is still a mismatch with the secondary data source.

Hi Tobias, The command is failing because your secondary data source has attributes, yet the main data source has elements. You'll need to change your main data source to have a repeating field with the four necessary attributes. Also, when you re-design your main data source, make sure that the order of the attributes matches the secondary ...

Hello! One option is to use Data Validation, and simply prevent people from entering non integer characters. That is, force them to only enter integers. Another option is to split this into two fields: one field for the numbers before the period/comma, and then one field for the two digits after the decimal Finally, you could try some wacky ...

You would have to read in the entire list of xmls stored in your form library (into a secondary data connection). Then, based on the username and date, generate the form (xml) name temporarily (store it in a field). Then try to find a match between the current form's filename and the list of existing filenames. If there is a match, display a ...