InfoPath Rule Inspector displays incorrect node sets

profskett — Wed, 16 Dec 2015 10:14:00 GMT

Hi all. I'm new here, so sorry if this topic has been discussed before - I couldn't find anything about it when I searched though. I am trying to create an InfoPath form for a particular Radiotherapy QA process which we do in our department. In the process, I think I have discovered an odd bug in InfoPath, and I was wondering whether anyone else had come across this before or if there might be a solution to it.

The problem I am experiencing is in the InfoPath Rule Inspector. I have created a number of conditional default values using filtered node sets, as described in the MSDN blog entry here. I have 3 different node sets, each of which is used when assigning the value to a different field in my form. However, when I look in the Rule Inspector, it appears as if there is only one filtered node set present, which is being used by all 3 of the dependent fields - as shown in the screenshot below:

Just in case it isn't clear what I mean from the picture itself: (ArcCheckqaSetupString | MatriXXqaSetupString) is one of the node sets I've used with a filter to set a conditional default value; DeviceCalNote, PinnaclePhantomNameString & qaSetupNote are the fields whose default values are set in this way, but, in reality, they are all dependent on different node sets, whereas it appears in the Rule Inspector as if they are all referring to the same one.

I know that the calculated default values for these three fields do actually refer to the correct node sets, as the form produces the correct (i.e. expected) result in each case when I preview it. It just doesn't seem to display the different node sets in the Rule Inspector. Does anybody have any idea why this could be happening, and/or if there is a way to fix it?

General

InfoPath Rule Inspector displays incorrect node sets