2260
Points
Questions
0
Answers
170
-
- 1429 views
- 6 answers
- 0 votes
-
- 1429 views
- 6 answers
- 0 votes
-
- 1429 views
- 6 answers
- 0 votes
-
You are good to go. Yes, put the child item on the Affected Items of the same ECO and set the revision. You can also add it to the redlines of the assembly, also on that same ECO. Don’t worry about the rev you see in the redlines. That is just the current revision of the item, if released. Not what it will be set to. Try it.
- 1503 views
- 1 answers
- 0 votes
-
Unless you can get that XML in the format of either PDX or AXML via a style sheet you would be looking at a custom program to parse the xml. Agile has out-of-box import capabilities for those two xml formats. They also have web services that take xml. But of course, it would be Agile’s format of xml.
- 1603 views
- 2 answers
- 0 votes
-
- 1173 views
- 3 answers
- 0 votes
-
- 1264 views
- 1 answers
- 0 votes
-
Try restarting the Agile services. That may unlock it. Otherwise, disabling and enabling the field isn’t going to do anything for you. The only reason I can think of that the field is locked is that it is used in search or other criteria. In that case, Agile should be giving you a message to that effect.
- 1248 views
- 3 answers
- 0 votes
-
- 1913 views
- 2 answers
- 1 votes
-
- 1861 views
- 3 answers
- 0 votes