hexagon logo
Register Sign in
  • State Not Answered
  • Replies 9 replies
  • Subscribers 11 subscribers
  • Views 134 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
    Hey Jesper,
     
    I think you are misinterpreting my comment. You can still have multiple unique Requests with a common "Results set name." But you can't use a "Results set name" if another object exists in your template with the same name. So when creating a new template object/variable, you'd have to check all Requests to see if one has a "Results set name" that matches the object/variable, and vice versa.
     
    I had a state variable with the same name as the "Results set name" I chose, and that Request did not have its data saved to file. Added an extra underscore to my "Results set name", and it fixed the problem. Let me know if you can't reproduce this issue, or need additional info.
Reply
  • 0
    Hey Jesper,
     
    I think you are misinterpreting my comment. You can still have multiple unique Requests with a common "Results set name." But you can't use a "Results set name" if another object exists in your template with the same name. So when creating a new template object/variable, you'd have to check all Requests to see if one has a "Results set name" that matches the object/variable, and vice versa.
     
    I had a state variable with the same name as the "Results set name" I chose, and that Request did not have its data saved to file. Added an extra underscore to my "Results set name", and it fixed the problem. Let me know if you can't reproduce this issue, or need additional info.
Children
No Data
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement