-
The latency you're seeing is likely due to two things: data connections and rules that execute on load, and rendering the view in the browser. You could try to address both by creating separate views for the user. This means that the form opens and shows only the bare necessities and only queries the bare minimum data needed on load. Then as ...
-
We recommend using qRules; here are two video demos you can check out.
http://www.youtube.com/watch?v=mpueygXbV-A
http://www.youtube.com/watch?v=WftCp_EbcCU
Using qRules makes things easier, saves you from having to write code or any other development-like obstacles.
-
Unfortunately, I believe this is a limitation of webforms (users overwriting each other's changes).
-
Hola,
Podrías explicar con más detalles?
Nos gustaría ayudarte, pero no entendemos tu pregunta.
-
Yes, the general steps would be the following:1. Create your secondary data source to retrieve data from your SharePoint list. (no qRules) You will need to make sure you bring in the ID field.
2. Look at the data source brought in by InfoPath. Now create your schema in the main data source, so that the fields match the secondary data ...
-
Ok, great. This means that if you create a data connection to retrieve data via Active Directory, you'll have all of the user's active directory properties available in the secondary data source. Within that set of data, are you getting a user role, department or something similar?
-
I don't know if this will help you, but we have a Change History XTP, available in the Downloads section, here:
http://www.infopathdev.com/files/folders/templateparts/entry60774.aspx
and here
http://www.infopathdev.com/files/folders/templateparts/entry60775.aspx
-
I have done what you propose; that is, storing both the ID and the display name in the form, and promote the display name as the column in the form library.
You might also try having the column defined as Managed Metadata. (Screenshot attached.) Perhaps this enables SharePoint to treat this like a lookup column? I haven't tried myself, but ...
-
How are you determining the user's role? Do you have a way of querying active directory, are you querying a SharePoint list that contains a list of users and roles?
I think that's the tricky part. The rest is easy, since InfoPath provides a way to add Formatting logic, so you can disable a field if a certain condition is satisfied.
-
You would need to have a parent-child relationship. That is, the non repeating data of your form would belong to the parent table, and the repeating data in your form would belong to the child table. You would need a key to define the relationship between the parent and the child, but this allows you to have a one (parent) to many (children) ...