CaseComplete Community

Sharing ideas about CaseComplete® and Use Case modeling
Welcome to CaseComplete Community Sign in | Join | Help
Home Forums

Error in Custom Report

  •  12-03-2007, 1:39 PM

    Error in Custom Report

    I’m having difficulty troubleshooting an error message from the “Generate Word Report” tool, which reads “The requested member of the collection does not exist”.

     

    How do I determine which collection is being referenced and which member?

     

    The custom report is a variation on the "CompleteByPackageFull" report and is enclosed below:

     

    =======================================================================

    $Name

    Use Case Model

    Complete report shown in Package Hierarchy Order, Full Descriptions

    Version 1.0

    Prepared by:

     

    December 2007

    Contents

    1      Name. 2

    ID Name. 2

    ID Name. 2

    ID Name. 3

    Glossary. 4

     

    $outlinePackages

     

    $Name

     

    $Description $DeleteEmptyLine

     

    Custom Fields

    Value

    $tableCustomFieldsSortName $Name

    $Value

     

    Notes

    Date Added

    $tableNotes $Description

    $DateAdded

     

    Related Documents

    $tableRelatedDocuments $Name

     

    $repeatActors

     

    $ID $Name

     

    $Description

     

    Custom Fields

    Value

    $tableCustomFieldsSortName $Name

    $Value

     

    Goals

    $tableGoals $Description

     

    Notes

    Date Added

    $tableNotes $Description

    $DateAdded

     

    Related Documents

    $tableRelatedDocuments $Name

     

    The following are the use cases that this actor plays a role in:

     


     

    ·        $listUseCasesSortName $Name ($ID)


     

     

    $endrepeatActors

     

    $repeatUseCases

     

    $ID $Name

     

    (Priority $Priority): $Description

     

    Details

     

    Parent: $Parent

    Primary Actors: $PrimaryActors

    Supporting Actors: $SupportingActors

    Preconditions: $PreConditions

    Success Guarantee: $PostConditions

    Level: $Level

    Complexity: $Complexity

    Use Case Status: $UseCaseStatus

    Implementation Status: $ImplStatus

    Assigned To: $AssignedTo

    Release: $Release

     

    Custom Fields

    Value

    $tableCustomFieldsSortName $Name

    $Value

     

    Flow of Events

    $tableFlowOfEvents $Prose $DeleteEmptyLine

    Main Success Scenario:

    1.        $listSteps $Description

     

    Extensions:

    $listExtensions $NumberedDescription

     

     

    Notes

    Date Added

    $tableNotes $Description

    $DateAdded

     

    Open Issues

    Assigned To

    Resolve By

    $tableOpenIssues $Description

    $AssignedTo

    $ResolveBy

     

    Related Documents

    $tableRelatedDocuments $Name

     

    Referenced Requirements

    Type

    ID

    $tableRequirements $Name

    $Type

    $ID

     

    $endrepeatUseCases

     

    $repeatRequirements

     

    $ID $Name

     

    (Priority $Priority) $Description

     

    Details

     

    Parent: $Parent

    Type: $Type

    Status: $Status

    Assigned To: $AssignedTo

    Release: $Release

    Source: $Source

     

     

    Custom Fields

    Value

    $tableCustomFieldsSortName $Name

    $Value

     

    Notes

    Date Added

    $tableNotes $Description

    $DateAdded

     

    Open Issues

    Assigned To

    Resolve By

    $tableOpenIssues $Description

    $AssignedTo

    $ResolveBy

     

    Related Documents

    $tableRelatedDocuments $Name

     

    Use cases that reference this requirement

     

    $tableUseCasesSortName $Name

    $ID

     

    $endrepeatRequirements

     

    $endoutlinePackages

     

    Glossary

    The following table defines the terms and acronyms for $Name

     

    Term

    Meaning

    Aliases

    $tableGlossary $Name

    $Description

    $Aliases

     

    =======================================================================

     

     


    - John
View Complete Thread