-
Is this in Office 365? Or an on-prem server? If Office 365, these web services can't be accessed from a browser form. If this is an on-prem server, there are settings that can be changed to allow access.
-
I took a look at your flattened data - and from the sample data, you wouldn't really need any special formatting, right? The parent doesn't repeat for each child. I'd just add a little expression box as some padding to indent the child question number, hide if child != 1, for example....
-
If you are setting the field to space characters, it won't be blank You can just leave the Value blank in your rule to set it to blank.
-
I was just wondering how you'd determined that it had content in it - mine doesn't seem to (yes, I also checked in the browser). Can you save an XML file from the form where you think the RT has content so we can verify that?
-
This doesn't reproduce for me - I have a rich text box on my form, and added an expression box with an expression to check if the field is blank (my:field1 = ""). It returns true when there is no content in the RT field. If I type content in and tab out, the expression box returns false.
Do you have any other rules that ...
-
If you are going to use code to populate the main data source, I'd make the main data source reflect the true data structure. I'd have a parent group, with the repeating child group inside - then use code to populate the parent item and the child items for that parent. This makes layout simple - your layout now matches your data structure ...
-
I'm not being clear. Unless the data the user enters is in the main data source, the data won't save. I'm guessing you want the user to answer each question?
-
Oh, sorry, I hadn't seen this post. I'll see if I can reproduce this later today. SharePoint is also 2010?
-
Ouch, this is what I was afraid of. The issue with this is that you just can't create a filter here that will work. I'm sorry - I've tried this in the past, where the data comes from two separate data sources like this, and the best work around I've arrived at is using faux hide / show sections, where I query the secondary ...
-
Yuck, thanks for letting me know. I dislike "mystery" issues.... :)