-
It sure sounds to me like there is either a rule at fault or the controls aren't correctly bound. Can you attach a copy of the form under the Options tab in a reply?
-
So - you are promoting the account id field and then the workflow sends the email? I'd assume that would work, and am surprised it doesn't. Is there an error from the workflow?
-
To promote repeating data to SharePoint libraries, you need to use the "merge" option when promoting the field. You will likely need to add a rule to the dropdown where you pick Title to set the account id and display name fields in the people picker. Is your Reviewer / Secondary Reviewer column in your SharePoint list a person type?
-
Hey, Catharine, how are you? If you aren't using any commands that require the Admin option (there are very few) just use the sandbox injection option (even if admin deploying the form). Can you try that?
-
If you'd like me to take a look at the form, feel free to attach it under the Options tab. Or maybe provide some additional screenshots - sorry, I'm having trouble guessing what the issue may be here.
-
I'm wondering if your second condition is the issue - is this the same account id as the first condition?
-
I wouldn't think the title column from your secondary data source has a URL, would you? I'd assume that is why it goes to "about:blank", wouldn't you?
-
Something else in your form must have caused the issue - I use preceding-sibling in conditional formatting all the time in browser forms. What is the XPath expression you are trying in your condition? I'd expect, on the repeating table or section (if this is a SharePoint list connection - your relative XPath may be different) something like ...
-
Are you using the Hyperlink from the Insert tab on the ribbon? Or from the controls? It sounds to me like you want to use the Insert > Hyperlink and then you can bind that to your field that has the URL.... Do you have a column in your secondary data source with the URL to the item?
-
Sure - you can use conditional formatting for this. Is the total scores info in the secondary data connection, so you can sort by this when the data is returned to the form? If so, you can just use a count of the preceding sibling to hide rows after the first ten.