-
I'm guessing that the issue is specifically with hiding rich text boxes. Same thing happens for me - but you can put the RT boxes inside sections and they will show / hide correctly. You don't have to create a bunch of new fields - you can bind the sections to ReasonXI or to the RT Field
-
One thing you could do is put the ReasonXI field on the form and publish and verify it is being set to 1, 2, etc as anticipate by your formatting condition in the browser.
-
Found it, thanks. I'll try it on my Office 365 site later today.
-
Can you tell me a field that has a formatting rule on it? I started clicking through the text boxes looking for formatting rules, but I'm not finding any.
-
Oh yuck. Do you mind attaching a copy of the form (or email me via the forum - I'll reply & you can send me the form)? You can attach a copy under the Options tab in a reply. It will be later today, but I'll try on my Office 365 site, just to see if it works there....
-
Browser or Filler? Does it work in preview but fail in the browser, for example? If it also fails in preview, can you attach a copy under the Options tab in a reply and I'll take a look?
-
Try replacing your current calculated value with this: xdXDocument:GetDOM("Change Control Approvals")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW/d:User[../d:Title = "SVP, Collections"]/pc:Person/pc:DisplayName
I don't know why, but when you added the filter, InfoPath added the full path to the ...
-
Any chance I can see a copy of your form? You can attach it under the options tab in a reply.
-
I'm wondering if the code sample here might be helpful: https://docs.microsoft.com/en-us/office/troubleshoot/office-developer/encode-and-decode-attachment-using-visual-c-in-infopath-2010
-
Are you working on a list form? Or a regular library form? The only reason I can see that you'd be having a hard time doing this would be if the form is a list form or was created from an existing data source of some kind.