InfoPath Dev

Just emailed you via the forum with a link :)

You probably need to be using "current" in that expression somewhere. I can't guess without seeing the form.

You'll need to use rules for this. On the field with the three options, add your logic for setting the date for each condition (i.e. field1 = new, do this, field1 = old, do that). You'll also need to add submit logic to update the date for your additional logic. Whatever the button or action in the form that is taken to indicate ...

Hmmmmm. Since it wasn't installed, but instead copied over, I wonder if there is something else in the web.config that needs to be updated. For the DBXL Admin Tool, there is a service that you can use to republish that which may help - from the DBXL home page, /QdabraWebService/DbxlAdmin.asmx that has a method for publishing DAT. You'll ...

Unfortunately, list forms can't be changed to connect to a different list via the InfoPath UI - I think there may be a way to do it in the source files, but it isn't going to be straightforward. Probably best to just customize your new list in InfoPath.... Unless you want the same list fields? In which case, I think if you save the list as ...

Hey, Jasmin - I missed your follow up question. Sorry about that. I'd probably use a helper field for the filtering - you don't include too many details about what you are hoping to achieve, so I'm attaching a simple sample with one approach. As to "SumIf" - we just use filtered XPath for that - you'll see that in this ...

Perfect, thanks! This message is telling you that you changed the data type of one of the promoted fields. Was that intentional? If not, change it back. :) If so, in design mode, under the File menu in the ribbon, on the Info category, select "Advanced Form Options". Navigate to promoted properties. Remove the promoted property named in ...

Is this a list form? You might want to save a copy of the form for a backup, and then refresh the fields - I think that is under the data tab in a list form. If it isn't a list form, maybe you could post a screenshot showing the error under the Options in a reply.

The default location on a machine with qRules installed is C:\Program Files (x86)\Qdabra Software\Qdabra Rules Library\DLLs, although depending on where qRules was installed, this could vary. If you save the form template as source files (Publish > Export source files) it should also be present in the source files. If dropping the DLL into the ...

To relink, you should be able to select the file with the incorrect Template URL in the list in the relink view, and then select the option to relink the form. Honestly, not sure how you are ending up with these unless 1) You are submitting from preview or 2) you have a non-published version of the form in your InfoPath cache, in which case, refer ...