Hi, I have had a few issues around cyclical dependency, the most recent yesterday which involved the inability to activate a script calculation view which called procedures which in turn referenced a table type in a .HDBDD. Selecting the calculation view, HDBDD and procedures and trying to activate them together didn't work, nor did forcing activation. I commented out the call to procedures to get the activation of the .HDBDD through.
In my earlier posted example I had to work back through related objects, deleting to see which prevented .HDBDD activation, then activate .HDBDD and then restore the deleted artifacts. Not nice.
I think the rules governing activation of .HDBDD are too strict, as activation can even fall foul of ODATA services consuming information model views which upset .HDBDD.
Did you product the graph as suggested in the indexserver trace? Have you commented out recent changes made to Procedure A to see if you can activate? Comment out all code? Comment out reference to Procedure A one by one? Any changes made to interface (in and out definitions) of Procedure A?
Far more developer friendly if a graphical representation of dependency was available within Studio itself.
Grateful if Thomas Jung can comment on any awareness of issue internally. I wonder if any changes to .HDBDD activation made an appearance in Rev.72?