Hi Archan,
I am unable to recreate this behavior in my own environment. To learn more about the issue you could use server debug logs to better understand where this error is coming from. A blog written by labs regarding server debug logs can be found here. Is this issue happening on all requirements, or only ones you're adding through AML?
AJ
Hi AJ,
This issue is happening on all requirements, added through AML and through UI as well.
I followed the steps mentioned in the blog, I am getting two errors in the debug log:
Error 1:
<SOAP-ENV:Fault xmlns:af="">www.aras.com/InnovatorFault">
<faultcode>0</faultcode>
<faultstring><![CDATA[No items of type Report found.]]></faultstring>
<detail>
<af:legacy_detail><![CDATA[No items of type Report found.]]></af:legacy_detail>
<af:legacy_faultstring><![CDATA[No items of type 'Report' found using the criteria:
<Item type="Report" action="get" select="name,label"><type>generic</type></Item>
]]></af:legacy_faultstring>
</detail>
</SOAP-ENV:Fault>
Error 2:
<SOAP-ENV:Fault xmlns:af="">www.aras.com/InnovatorFault">
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring><![CDATA[Invalid object name 'RE_REQUIREMENT_DOCUMENT'.
Could not use view or function 'DERIVED_DOCUMENTS' because of binding errors.]]></faultstring>
<detail>
<af:legacy_detail><![CDATA[Invalid object name 'RE_REQUIREMENT_DOCUMENT'.
Could not use view or function 'DERIVED_DOCUMENTS' because of binding errors.]]></af:legacy_detail>
<af:exception message="Invalid object name 'RE_REQUIREMENT_DOCUMENT'.
Could not use view or function 'DERIVED_DOCUMENTS' because of binding errors." type="System.Data.SqlClient.SqlException" />
</detail>
</SOAP-ENV:Fault>
Hi Archan,
The first Report error is probably unrelated to the behavior you're seeing within RE. Have you made any modifications to any of the standard RE itemtypes? Even if you haven't would you mind opening, locking, and then clicking save, unlock and close? This could rebuild the view that exists behind the scenes if something had been modified previously.
AJ
Hi AJ,
Yes I did try changing the name of re_Requirement to Requirement, but that gave me some other errors so I changed it back to re_Requirement
