11.1 Change object Link modifications and Query Builder

[avillanueva]

I've been able to work around this issue using unions in QML but still wish there was a better way. When we went to 11.1 from 10.2, the way change objects were linked was fundamentally changed. All my query builder reports broke cause the joins were all different. As a result, I had to create a version of a report that grabbed data before upgrade and one that grabbed data after the upgrade. Tables were never merged but looks like they coded around it. Has this been addressed in 12 to merge the tables to give a complete history?

[JeffZemsky · Accepted solution]

@avillanueva The best practice is to plan to move your legacy links to the new Flexible association links.  We don't have a the firm release yet, but we will eventually deprecate the legacy links.  Moving these older changes would remove the need for the additional queries.

[avillanueva]

@JeffZemsky , so there is a step I need to do right? CS262354 indicates there is a tool to move the legacy links. I would have expected the upgrade to handle that for us since post upgrade, we were using flexible links though we have not varied from traditional or OOTB. Ok, I see that I've missed the memo and need to run the conversion tool. Thanks.

[JeffZemsky]

@avillanueva we do not automagically do that as if there are running workflows there are some extra steps and considerations. 

In Help you can find more detail on the Flexible Change link Conversion topic

[avillanueva]

@JeffZemsky you sell yourself short. I've always though of you guys as magicians. 

[JeffZemsky]

Wish it was all that easy 😂