jjlong - Tuesday, August 2, 2011 2:26 PM:
I'm attempting to create my first report in Aras. I'm trying to create a simple report which lists the packages and their dependent packages. I have developed the AML query I need using Nash, but am getting an "Error: 53 Permission Denied" error when I try to lay out the report using the designer tab on the Reports editor.
Has anyone else experienced this? Any advice how to get around the problem?
Here is how I recreate the problem:
1) From Administration, go to Reports and choose "New".
2) Fill in the form as shown using this AML query
<Item action="get" type="PackageDefinition" select="name">
<Relationships>
<Item type="PackageDependsOn" select="name"></Item>
</Relationships>
</Item>
3) Click the "Run Query" button
4) Select the middle "Designer" tab
5) Move the mouse over the words "Enter Value". The table row should turn blue. Then right click and select "Value..."
6) Double click on "name" beneath the first Item (i.e. row 2) and "Result/Item/name" will be placed in the "Expression" field
7) Select OK
8) The error occurs
BTW, I searched Google and found something which sounds just like my problem.
efreedom.com/.../Internet-Explorer-Script-Error-Message-Webpage-Permission-Denied
wwv.comanswer.com/.../internet-explorer-script-error-message-from-webpage-permission-denied
but I don't know what to do with this information.
aaasam - Wednesday, November 23, 2011 1:59 PM:
Jeff,
Were you ever able to get this resolved?
I have a "similar" kind of error message, which leads into an <AML> report building coding question.
I see you have several items at the "PackageDefinition" level, and within those there are additional related items at the "PackageDependsOn" level.
How do I find an example, or do you have one that will show me how to iterate (loop) through the items to build my report?
==========
Essentially, I have a report that could have 1 or more recipes for tasting + 0 or more contacts for that tasting session + 0 or more questions & follow-up question that pertain to the particular recipe that was tested by the individual contacts. Having one main form with 3 tabs below [Recipe] [Contacts] [Questions] which are all related back to the main form.
-Scott
jjlong - Wednesday, November 30, 2011 8:38 AM:
Scott,
I never got a resolution on the error, but I determined that it only occurs on my Windows XP laptop which is not an official platform. When I run the tool off my server (Windows Server 2008) I don't see the message. I also determined that on Windows XP it is not a barrier to using the tool; I've found it is just an annoyance.
If I understand your question correctly, you are having the same struggle I had trying to generate statements to loop through the relationship data. I tried a lot of things with the tool, and determined it can't be done completely in the tool. My conclusion was confirmed when I found this topic in the XSLT Report Tool Users Guide on page 23
Displaying nested tables for relationships.
To display the relationship Items for nested tables you will need to reduce the XPath to the relative path based on the context node for the <xsl:for-each> loop that the nested relationships table is in.
<xsl:for-each select="Relationships/Item">
<xsl:for-each select="related_id/Item/Relationships/Item">
</xsl:for-each>
</xsl:for-each>
So in the context of my AML query in the original post:
<Item action="get" type="PackageDefinition" select="name">
<Relationships>
<Item type="PackageDependsOn" select="name"></Item>
</Relationships>
</Item>
I used the report writing tool to construct the table structures and the outer loop, and then edited the stylesheet by hand to build an inner loop using paths relative to the items iterated in the outer loop. A snippet of the looping portion of my stylesheet looks like this, and the loops are in bold:
<xsl:for-each select="Result/Item[@type='PackageDefinition']">
<xsl:sort select="name"></xsl:sort>
<tr>
<td class="cellSolid" style="font-family:helvetica; font-size:8pt; padding:2px;" uniqueID="ms__id5" headerID="ms__id3">
<xsl:value-of select="name"></xsl:value-of>
</td>
<td class="cellSolid" style="font-family:helvetica; font-size:8pt; padding:2px;" uniqueID="ms__id4" headerID="ms__id2">
<xsl:for-each select="./Relationships/Item[@type='PackageDependsOn']">
<xsl:sort select="name"></xsl:sort>
<xsl:value-of select="name"></xsl:value-of>
<br></br>
</xsl:for-each>
<xsl:choose>
<xsl:when test="count(./Relationships/Item[@type='PackageDependsOn']) = 0">
<xsl:call-template name="nbsp"></xsl:call-template>
</xsl:when>
</xsl:choose>
</td>
</tr>
</xsl:for-each>
The outer loop statement <xsl:for-each select="Result/Item[@type='PackageDefinition']"> is an absolute path that iterates the Items, and the inner loop statement <xsl:for-each select="./Relationships/Item[@type='PackageDependsOn']"> uses a path relative to the Item to iterate the Relationship items (note the dot slash in the select attribute).
Does this help?
