Home > Forum > User Voice > Link in configuration SQL Source Pickers

Link in configuration SQL Source Pickers UNDER REVIEW
6

MVP

Hi,

In my opinion, the biggest advantage of BPS data sources is the ability to link to a selected element.

However, the disadvantage is much lower performance in advanced conditions, inability to join data, use union, and combine data from different content databases.

By changing the source from BPS to SQL, users lose the functionality of the link. Of course, we can achieve this in a different way, but it is not consistent, for example, with other pickers using a BPS source.

Would it be possible to introduce configuration options in the picker with an SQL source where we can map columns with ID, Appid, and dbid? Alternatively, a configuration where we return, for example, the entire constructed link (e.g., references to applications other than Webcon)?

In environments where we use several content databases, this would be very useful and would introduce greater consistency for users.

Regards.

MVP

Hi Karol

Thank you for bringing up this suggestion.

Providing an easy way to provide a link to other systems (e.g. contacts in Dynamics 365) reminds me of the time when I used MatchPoint to configure applications in SharePoint.
For lookup fields there was a way to provide an url with a placeholder that had been replaced by the Id.

A similar approach could be used by WEBCON.
Apart from the suggested placeholders (id, appid, dbid), it would be great to choose whether the preview is available or not.