-
Many to many is the problem. You could create a dummy table to connect them - something that is just an auto incrementing ID field. Add that field to your other tables so you can relate them to your new "parent" table. Does that make sense?
-
I am having such a hard time understanding what you are doing & trying to do.
Validation works in repeating tables. See the attached sample - if the data selected in any row is greater than today less 60 days, it is invalid.
My earlier suggestion was you might want to count all the valid dates in the form before enabling your submit button - ...
-
Hmmm - the problem I think is that you are trying to update secondary data in your form - which isn't really do-able. You'd need to copy the secondary data into the main data source of your form. Or you could have the user manually insert each row into the main data source and select which ShP list item the Qty refers to.
However, you do ...
-
So, it seems to me that you only need to submit to Software and SoftwareVerions out of the 4 tables listed, is that correct? And then the Servers & Software tables are to be used as lookups? Or can the user also submit new Servers / new ServerSoftwareVersions? That is, do you need to submit to the Server tables or are those just displayed for ...
-
Feel free to email your form to Support AT Qdabra DOT com if you'd like me to take a look - you should be able to just remove code and re-inject if you no longer need custom code, but it sounds like that didn't work for some reason. Reference this thread in the email.
-
You bet - glad you are up and running again!
-
The qRules DLL won't work via regular injection if you have custom code - but you can still use the DLL - just have to do it a bit differently than injecting. Here's a document on this - let me know if you have any trouble with it.
-
Hi - couple of things - instead of running the rules on FormLoad, there is a node in the QdabraRules data source called "finishedLoading" - run your rules on that with the condition that the node value is equal to true - since rules run before code, form load rules and qRules can be a little tricky.
Also in the QdabraRules data source ...
-
The validation rule needs to go on the date field in the repeating table itself. The first condition should be if the field is not blank (to prevent false errors).
Then add your second validation rule.
InfoPath won't let users submit if there are validation errors in the form. However, based on this description, it sounds like you may have ...
-
Run in debug to find out what's null - here's a blog post with info on how to run your code in debug.