hexagon logo
Register Sign in
  • State Not Answered
  • Replies 9 replies
  • Subscribers 11 subscribers
  • Views 136 views
  • Users 0 members are here
Options
Related

Missing components in request file

Stefano.Cassara
I have defined multiple requests, many of which share a common results name (so that all the components show up under a single name). The request file is missing many components. Are there limitations to the number of requests and components that can be grouped this way?
Parents
  • 0
    OK I just figured this out. If you keep the "Request Name" and "Results Set Name" the same when creating the request, A/View will check that the name does not already exist in your model/template, and thus won't allow you to duplicate the name.
     
    The problem occurs when you create a unique "Request Name", but choose a "Results Set Name" that matches another object in your model/template. It should throw a warning or error to not allow the Request to be created, as right now the Request is simply not written to the .req file.
Reply
  • 0
    OK I just figured this out. If you keep the "Request Name" and "Results Set Name" the same when creating the request, A/View will check that the name does not already exist in your model/template, and thus won't allow you to duplicate the name.
     
    The problem occurs when you create a unique "Request Name", but choose a "Results Set Name" that matches another object in your model/template. It should throw a warning or error to not allow the Request to be created, as right now the Request is simply not written to the .req file.
Children
No Data
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement