Skip to main content
avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
June 30, 2020
Question

CR to CN Links: How I Learned to Stop Worrying and HATE Query Builder

  • June 30, 2020
  • 1 reply
  • 2950 views

Actually, its a love/hate relationship, more hate. Well, they did it to me again. Upgrade changes things (flexible changes) but leaves you in a state where objects before the upgrade return in reports but nothing after. In this case, the addressedBy link was deprecated but the data was not moved. "You moved the cemetery, but you left the bodies, didn't you?" Yep. This means any report that had joined the two only sees pairs created before the upgrade (in my case 10.2 to 11.1). The new link is ChangeProcessLink but for some reason, I had to two step it to get results to show. I was able to get this join model to work but you need to use outer joins pointing toward the change request. This will return either links from AddressedBy or ChangeProcessLink in a single report. Between you, me and the poltergeist, I am shocked it worked.

CR-CN.png

1 reply

A
aaronjlarson14-Alexandrite
14-Alexandrite
June 30, 2020

That's interesting in your query solution.  I haven't tried that yet.  We did the same upgrade path you mentioned and ended up:

1) Using a migrator provided by PTC to migrate the AddressedBy links to the new ChangeProcessLink.  The catch was that the process has to be completed/resolved and not in-flight.

2) To deal with the CR/CN that were still in-process we ended up having to duplicate our reports, one to return legacy results (pre-upgrade) maintaining the AddressedBy join and one for post-upgrade using the ChangeProcessLink.  I'll have to review our join model and see if your solution can help us get back to a single report.

avillanueva
23-Emerald I
avillanueva23-Emerald IAuthor
23-Emerald I
July 1, 2020

Well, not so fast. Kudos to an astute colleague of mine. Reading CS227892 it would indicate that it might not work. Early tests did not try to display the CR data which later testing reveals as blank.  Thanks for the extra effort there PTC.  Can you send info on that migrator?

 

"Creating one report to display both Legacy Change Associations and Flexible Change Associations is not supported using the Query Builder UI"

Well, easy solution is to create a Union report. I know how to do those.

Terms & ConditionsCookie settingsAccessibility statement