InfoPath Dev

Inside the form? Sure - from the Insert menu, click Insert Hyperlink. You can set the link text to the word "here" and you can use a data source field for the value. If you don't already have a field with the link in it, you can add one to your main data source.

Sure. You just need to store the approver info in the main data source of the form - don't display it on the form - and then you can add form load rules to check the approver. I usually have a status field in the main data source too that I use to help track these things... If you want to get fancy, you can store that info in a SharePoint list ...

You need to set additional conditions. Usually I just do that in a single rule at the beginning of the submit rules - you could add a field to your form for an error message (if this is a browser form) or display a message box (if filler) and select the checkbox to not run the rest of the rules if the condition is met. Your rule condition verifies ...

Here's a link with some sample code that may point you in the right direction: https://support.microsoft.com/en-nz/help/2517906/how-to-encode-and-to-decode-a-file-attachment-programmatically-by-usin

I'm happy to help you with this - what would be simplest for me would be if you could attach the template under the Options tab in a reply and the I can help you directly with the rules.

Hmmmm - since the fields are required based on the form version, I'd probably actually leverage the form version number to determine them and to determine which controls to show - you could use a string comparison with a function to return the form version.... ...

Multiple selects are very hard to work with using regular rules. If you add a rule that sets the field the multiselect is bound to to blank, you'll end up with a bunch of empty nodes - InfoPath doesn't provide a way to delete the nodes. I don't think there is a way to do this without code or a third party tool like qRules, I'm ...

I don't think this is possible without using code (or an add-in like qRules) - the main issue is that the original multi-select is a repeating field (in the form's schema) and there isn't a way via rules to add new instances to the new multi-select to populate all the options that have been selected. What about using content types in ...

Here's a sample - save the file locally, right click and select Design. From there, preview and enter data in the data entry view, then switch to the Dashboard view and select a date. You'll find conditional formatting rules on the repeating tables to only display data for the data selected. Hope this helps!

Hey - I've had some similar issues and the only thing that's worked for me is creating the data connection as new, then when I convert to UDCX, overwriting the existing UDCX (or just updating the manifest manually to convert to UDCX, which is actually what I'm more likely to do) - Hopefully someone else will have a more helpful ...