It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×11,989
×5,900

question asked: Feb 18 '20, 10:12 a.m.
question was seen: 907 times
last updated: Feb 18 '20, 4:09 p.m.

Related questions

Changing URIs for Artifact Types and Artifact Attributes?

0
Mary Miller (87●2●32) | asked Feb 18 '20, 10:12 a.m.

Good day,


I have a question.  We had to change our naming convention for URIs to be used with Artifact Types, Artifact Attributes, Attribute Data Types and Values.

If we change the URIs, for these elements, would there be any unexpected issues? 

I know you cannot and should not change the public URI.

Sincerely

Mary 

Accepted answer

1
permanent link
Sean F (1.3k●2●52●162) | answered Feb 18 '20, 10:31 a.m.

Hi Mary,

If you change all the matching URIs across all the projects so they are still matching then after the change is complete everything should work just like before the change..

You can export/import data across projects and do cross project reporting like before.

The only think you might need to do is a schema update to the data warehouse.

>Reports>Build>Data Source>Refresh

and then the data

https://xxxx.clm.ibmcloud.com/dcc/web
Run Update

before running any JRS reports

Mary Miller selected this answer as the correct answer

One other answer

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Davyd Norris (2.6k●2●17) | answered Feb 18 '20, 4:09 p.m.
Just be aware if you've ever done any ReqIF import or export - that means an external system will have the old URIs and they will need to change them as well.

Also LQE makes a lot of use of the URIs, and so any Report Builder Reports based on an LQE data source will need to be rebuilt. The SPARQL query embeds the URI

Your answer

Register or to post 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.