General

Re: Design Checker error that won't go away

rayzermatic — Wed, 06 Jan 2016 16:59:00 GMT

Well...I guess, from what I've found since I started this thread, is that "orphans happen." LOL

Seems that it's just the ones that point to a non-existing data source make all the noise. haha.

Re: Design Checker error that won't go away

Hilary Stoupa — Wed, 06 Jan 2016 16:30:36 GMT

When I went digging through a form manifest to get the XML for my initial reply - I found an orphan right off. My sample was one. :)

Re: Design Checker error that won't go away

rayzermatic — Wed, 06 Jan 2016 16:18:16 GMT

yep... I know I have indeed done both of those.

so...now I have a new strategy, and will delete the rules before deleting a field containing them or a data connection.

I know I must have billions of little orphans. haha that may be a bit (quite a bit) of an exaggeration. But...I bet I have a lot of em. :)

Thanks again Hilary for sharing a bit of your wealth of experience and information.

Ray

Re: Design Checker error that won't go away

Hilary Stoupa — Wed, 06 Jan 2016 16:11:09 GMT

I think this can happen if you remove a data connection without first removing all the rules - I've never tried to reproduce it tho..... I've also wondered if it might happen sometimes when we remove a field w/out removing the rules first, but again, I haven't invested any time trying to track it down. :)

Re: Design Checker error that won't go away

rayzermatic — Wed, 06 Jan 2016 16:04:09 GMT

So, what did I do wrong to create the orphan rule.

Maybe that's what I need to know so I don't make more of em.

Re: Design Checker error that won't go away

Hilary Stoupa — Wed, 06 Jan 2016 16:00:50 GMT

When you end up with a orphaned rule like that, often a manifest edit is your only choice, unfortunately. Glad that fixed it. :)

Re: Design Checker error that won't go away

rayzermatic — Wed, 06 Jan 2016 15:55:11 GMT

Yep...that did it.

I was hoping to not have to do that, but I did according to your instructions.

Thanks,

Ray

Re: Design Checker error that won't go away

Hilary Stoupa — Wed, 06 Jan 2016 15:28:19 GMT

So - in the manifest, the rule set will have an identifier. Usually, once I find that, I search for that.

So - if the rule with the old reference is: <xsf:ruleSet name="ruleSet_5">, do a search for ruleset_5. If the only occurrence is in the xsf:ruleSet node, you can just delete that node from the manifest, and, in fact, this is probably the only way you'll successfully remove it.

But, if you find a ruleSetAction for it, you'll need to remove that too - or that can give you a hint as to where you can find this in your form: <xsf:ruleSetAction ruleSet="ruleSet_5"></xsf:ruleSetAction>

Design Checker error that won't go away

rayzermatic — Wed, 06 Jan 2016 14:47:18 GMT

Hi,

I recently changed some web services references in a form. But when I try to run Design Checker, It keeps finding an error. I have gone through every rule I can find and can no longer fins any reference to the old webservice. Yet Design checker still finds references to the old code.

I outputted the form as source and in the manifest file, I still see the old references, but when I go to find those in the actual form, I cannot find them. (of course it would help if the rule reference numbers found in the manifest, were visible in the form. (or maybe I just don't know how to see them.))

Anyway, correct me if i'm wrong, but it looks like InfoPath didn't delete the old rules, but just hid the reference to them and the old rule stayed in the form. I haven't tried deleting them in the manifest and resaving yet, as I really don't like doing that. Is there another way to get rid of these old rules?

Thanks,