datalynxview field: wrong datalynx instance ist used for filtering patterns

[dasistwas]

When I add a datalynx view field pointing to a "external" datalynx instance to a datalynx instance then, the pattern of the current datalynx is filtered instead of the external one:

Pattern used in the view of the external datalynx instance:

#{{viewlink:Verwaltungsansicht;Zum Eintrag in der ExpertInnendatenbank;eids=##entryid##;}}#

This pattern does not refer to the external instance, but to the same instance where the datalynxview-field is used.

[dasistwas]

additional info: viewlink is wrong, ##entryid## is correct. So the view "Verwaltungsansicht" is pointing to the current datalynx, (it happens that boths views have identical view names) but the entryid is used from the external datalynx (which is correct)

[michaelpollak]

I looked at that and it is quite tricky.
When we see a tag we check what views are used by looking for the dataid in the views table (get_all_views). You at that point want to add another dataid (d in the urlparams) that we have no access to at the moment.

Easiest way I was able to test is to add the dataid d as a specified urlparameter, extend your link like this:

#{{viewlink:Verwaltungsansicht;Zum Eintrag in der ExpertInnendatenbank;d=???|eids=##entryid##;}}#