-
I did a webinars on this "parent-child" scenario in May: http://youtu.be/Buvgtg3ZCHI
Bottom line: there are several ways to do this.
-
Nope. You have to rebind the fields. You could create a "starter form" that includes common fields and reuse it over and over again. That's a best practice.
Another approach is to export the source files, but the view and the data source (schema) are in separate locations and you would need to also copy sections from the ...
-
I'm not sure I understand. You've got a content type that maps to site columns which you want to hide? Hide from where? The view?
-
Can you add a new field and use the concat function to concatenate the fields into one big field that the Nintex workflow refers to?
-
I suppose you could do a double submit and add the status field setting after the first submit which won't succeed if the form is invalid (therefore it won't get set). The second submit just submits the form again with the status field set. A bit of a kluge but probably easiest solution.
Another random approach. If you're required ...
-
This isn't supported out of the box.
You can use our qRules or DBXL accelerators to do this. qRules is a plugin and DBXL is a Web service. Unfortunately, neiter of them work with Access.
Sorry,
-
Certainly, it depends on what's installed on the clients. InfoPath 2003 won't open in the browser, so it will launch whatever's on the client. And if InfoPath 2003 isn't installed it will open whatever's there.
I don't know of a simple way to do this. My advise: just rewrite the jscript or remove it and add qRules. ...
-
Is this an InfoPath question?
-
If you're using a browser-based form (not the InfoPath filler), you need to use a Web service and a UDCX file. Your UDCX file should be configured with credentials that will access the other machine. If it's a separate domain, you may need to use SSO or Kerberos to configure the credential passing.
If you are using an InfoPath filler ...
-
Don't query on load. Add a rule (for example, on a button) that includes two actions: 1) set the value of the field under the secondary data source's queryFields and 2) query the data connection. That will filter your forms just fine on Office 365.
Gotta love out-of-box!