Windchill Object Initialization Rule

[bbusschers]

I want to update one of the object initialization rules.


- I download the xml file

- I edit the file and save it again

- I go to the Object Initialization Rule manager again

- I select the rule, which I want to update, and select edit

- I browse to the edited XML file

- Select "OK"
although I have the authorization to update the rule I receive the following
error message:
ATTENTION:
The content of the selected XML file is not valid.
A parsing error has occured.

I have tested the functionality by selecting an unedited xml file,
but I receive the same error message.
What I am doing wrong?
Thanks for the help.




With kind regards,,


Bert Busschers



Sr. Mechanical Designer/CAD Administrator
ME/ID Department


[cid:image001.jpg@01CEE12C.F7243940]


Lelyweg 10 - 7602 EA Almelo - The Netherlands
+31 546 535209 (tel)
+31 546 535299 (fax)
Bert.Busschers@bench.com<">mailto:Bert.Busschers@bench.com>
www.bench.com<">http://www.bench.com>

[MichaelSchumach]

I am having the same issue in Windchill 11.0.   I downloaded the site level OIR for "Part" and simply tried to create a new OIR at the product context level using the same XML just downloaded from the site level and get the same error as this described in this post.

**** Error message****

The content of the selected XML file is not valid.
A parsing error has occured

****

I did not see a resolution to this post.   Is there anyone with some ideas of why the error occurs and how to resolve it?

thanks

[adeshmukh-2]

Can you check the method server logs for the detail error? What is the change that you made to the OOTB file?

If possible, attache the OIR. I can check if I get the same error.

[MichaelSchumach]

Thanks for the reply.   I did get some feedback from PTC support.  There was an AttrConstraint for the id="number" that was incorrect.  At least when comparing it with the PTC OOTB rule.xml support emailed to me.

Not sure why the rule.xml we have in our implementation of Windchill 11.x is incorrect.  We have been on Windchill since 9.1 and maybe this is something that happened from the last couple migrations.

The attached xml shows the AttrConstraint commented out (id="number"  booleanbranch).  I replaced it with a 'value' tag and the OIR now loads as expected.