-
So, your Skill list - does it include the subcategory? I'm thinking you'll want to just have your skill list on the form and use some XPath for formatting make things appear grouped.
-
Hi - you have to add the child tables and create a relationship. So, when you first connect to the DB in the wizard, you should be able to add tables there.
-
Hi - I just see the clicked events for a bunch of buttons here - no actual code. Any reason you can't use the built in rule action to open another form - that is, is this a browser form? If it is a browser form - could you just include a hyperlink to the new form? I'm wondering if there is a way around using code for this for you.
-
Did you get the email I sent you with it attached? Perhaps the file type is blocked- attaching here.
-
I replied to your email - this was in an email Jo-Anne sent directly to you.
-
To add to what Ernesto has said - the SubmitToSharePointList command also uses the SharePointURL in the mapping file for the actual submit - so you'd need to update that URL as well.
-
I've been trying to figure this out lately too - it seems that IPFS considers the form to have changed (even if the data hasn't changed) any time it has to post back to the server. The only thing I can think of is to disable Save / Save As and use Submit rules. You could add a close button to the form that closes with no prompt and just ...
-
You can have custom code and qRules in a form together - here's a link to a document outlining this. If you have a form with qRules and commands that you now wish to add custom code to, you would not need to add the data connection to the QdabraRules XML yourself - you would need to add the code in the document to your custom code file and add ...
-
I believe Jo-Anne sent you a sample form demonstrating this technique. Did that resolve the issue for you?
-
They have to go in the same repeating group. If you need to set them to existing values in order to update existing items, you can use other form logic.