Tridion Dynamic Linking has built in proximity logic, that means that if the same component is on two pages, dynamic linking will link to the page which is 'nearest' the source page containing the link (using the algorithm described in the docs).

We are using DXA 2.0 and it seems that this proximity logic is not being applied when resolving links on a page returned from the Model Service. There doesn't seem to be any way to control which page links resolve to, which is a big problem for us as we have many subsites within a publication which reuse common content items, within their own subsite context page - the dynamic link within a subsite should thus always be to a page within that subsite.

Having checked the code, it seems that the page context is never taken into account when resolving links in DXA, which seems like a big omission. Am I missing something, or is there really no way to leverage proximity logic when resolving links in DXA 2.0?

Has anyone else encountered and/or worked around this issue?


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.