Skip to main content
P
pmorey1-Visitor
1-Visitor
February 13, 2015
Solved

Trying to branch an existing document

  • February 13, 2015
  • 3 replies
  • 2677 views

I am trying to branch an existing document to a new document. My ViewSet is set to document author. To do so, I start with a query and select a document of the same type. In this case, it is a requirement specifications. I highlight the desired document, go to the top menu and select "document", select the "branch" option in the drop down, and select a destination project. I have tried the "as of" "now", and other options. I have not selected the "also branch" options.

I get the following "PTC error" - "MKS124311: No valid initial states for type "requirement specification". Can someone please shed some light on this error and how to resolve it?

Thank you,

Phyllis

    Best answer by pmorey1

    Thank you everyone for your response. We have resolved the issue. It was related to adding mandatory fields to existing document formats. When we removed the "mandatory" requirement, we were able to branch successfully.

    Thank you again for your support and suggestions.

    Regards,

    Phyllis

    3 replies

    K
    KaelLizak16-Pearl
    16-Pearl
    February 16, 2015

    Hello Phyllis,

    It sounds like this is a problem related to having a mandatory FVA field on your content items (in this case a Requirement). I would suggest contacting PTC Integrity Support in this case to investigate, and add you to a defect resolution request, possibly for RFC 171454, or for RFC 967112 (or both). The typical culprits for the mandatory state in this case are either the field Category or the field ALM_Text.

    Regards,

    Kael

    P
    pmerkle5-Regular Member
    5-Regular Member
    February 26, 2015

    Hello Phyllis,

    just an idea: have you checked that you have the rights to create a new Requirement Specification?

    Regards,

    Peter

    K
    KaelLizak16-Pearl
    16-Pearl
    February 26, 2015

    Peter's idea is also a good one. Can you create Requirement Specifications in other ways?

    It might also be that you have the rights, but that there is a mandatory field which you haven't checked. Having said that, I still strongly suspect the issue noted in my first response.

    Please let us know what you find.

    Regards,
    Kael

    P
    pmorey11-VisitorAnswer
    1-Visitor
    February 26, 2015

    Thank you everyone for your response. We have resolved the issue. It was related to adding mandatory fields to existing document formats. When we removed the "mandatory" requirement, we were able to branch successfully.

    Thank you again for your support and suggestions.

    Regards,

    Phyllis

    Terms & ConditionsAccessibility statement