Why are OSLC update requests causing artifact links to disappear?
I am modifying a Capability workitem's "Planned For" attribute using OSLC requests from VBA. When I modify the attribute using the following request, all of the linked items under the "Links" page disappear.
I am using the following headers:
And I am sending the request to the following link:
When I modify the same workitem/attribute using the web GUI, this does not happen. Why is this happening and what can I do to avoid it?
|
4 answers
Its probably expecting content-type=application/rdf+xml Comments
Derek Bonderczuk
commented Feb 13 '20, 3:51 p.m.
Nope
<?xml version="1.0"?>
<oslc_cm:error xmlns:oslc_cm="http://open-services.net/xmlns/cm/1.0/">
<oslc_cm:status>406</oslc_cm:status>
<oslc_cm:message>Content type 'application/rdf+xml' is not supported.</oslc_cm:message>
</oslc_cm:error> |
Try OSLC-Core-Version=1.0 Comments
Derek Bonderczuk
commented Feb 13 '20, 3:32 p.m.
When I try that, I get this as a response:
|
you may need to GET the resource, add your property then PUT to do the update. a PUT without a GET may be updating the whole resource, not just patching the properties you changed. Comments
Derek Bonderczuk
commented Feb 13 '20, 12:29 p.m.
But if thats the case, then why aren't any other attributes changing? Its just the links that are changing when I change any attribute.
|
Try:
<rtc_cm:plannedFor rdf:resource="https://<server>/ccm/oslc/iterations/_HaogPoLeEemIA4r_U-X20w"/>
Comments
Derek Bonderczuk
commented Feb 13 '20, 8:51 a.m.
I just tried it and the same thing happens. The workitem is updated and the links disappear. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.