While creating an eQL report (documents reported by its Work Breakdown Structure), I came across this error.
this message is new to me. Can anyone explain what I'm missing?
The below is the query.
START WITH Document SELECT Id, Code, Revision, Attributes["Global", "Work Package Breakdown"].Value WBS WHERE Attributes["Global", "Work Package Breakdown"].Value = @Attributes["Global", "Work Package Breakdown"].Value ORDER BY Code
The @ symbol used to define variables within eQL reports. This is typically used to allow a user to enter data to refine the search rows returned. This error indicates that ALIM is expecting you to define this variable within the report. One thing is that the name you have for the variable is not what one would normally see in a report.
What is it that you are trying to do with this report?
Thank you, Michael for the response!
We have projects which have multiple Work Package Breakdown structure, which is one of the attributes we have in the container. While QA checking, we found several containers have wrong WBS structure and had to pick up all the containers which are assigned in the wrong WBS. That's why I'm trying to filter documents using the attribute only.
I tried running the report with Project filter and add the attribute in reporting column ---> this way we need to run the report project by project. (what about someone used the WBS for other project?)
Does this help?
I think you could use the eQL (Which is very close to what you had):
START WITH Document SELECT Id, Code, Revision, Attributes["Global", "Work Package Breakdown"].Value WBS WHERE Attributes["Global", "Work Package Breakdown"].Value LIKE @WBSCodeORDER BY Code
Then set up the variable @WBSCode in the Report Designer Define Parameters screen. You can also setup a default value for this variable on this page as well.
When you run this report in Director or Web the end user will be able to enter the WBS code and have the choice to use a wildcard in their search.
Hope this helps and addresses what you were looking to accomplish.
Answer Verified By: Vivien Lee
Many thanks, Michael
This works perfectly well! (using LIKE in where)