Completed

Standardize TARGIT URLs with Embedded Links

The way TARGIT currently builds out embedded links (using 2 hash-signs) is an incorrect URL. The information that appears after the first hash symbol is a fragment identifier, which can only be interpreted by the local web browser and not passed to the remote web server. The second hash sign breaks the URL, as a fragment cannot have a '#' in it.

My company and I have been trying to embed TARGIT dashboards in our mobile CRM platform, but the broken URL is preventing us from accomplishing this. I would imagine that other companies are facing this dilemma, and think that TARGIT should standardize URLs to be compatible across all browsers, in accordance with common web practice.

6

Comments

3 comments
  • Official comment

    Hi Meagan,

    From the TARGIT 2023 October release, embedded links will work with both '#/' and '##'.

    https://community.targit.com/hc/en-us/articles/10708693378588-Changelog-2023-October

    https://community.targit.com/hc/en-us/articles/360017721237-Generic-Embedding

    BR / Ole

  • Hi Meagan,

    We use the # in the fragment to identify embedded links in TARGIT. We have many customers running successfully with these URLs in 3rd party systems and don't consider this a bug and the URL to be incorrect. Unfortunately we cannot support all 3rd party systems at the moment. 

    Best regards / Ole

    0
  • Hello Ole Dyring

    We initially submitted this "issue" while working with embedded links in a 3rd party app, but have since ended use of this app, so everything was working as needed. Unfortunately, we are having another issue with embedded links with "#", while using iOS. I am not sure exactly when this started, but it seems to be occurring on multiple iOS versions (tested with 15 and 17). The issue is that when clicking a link to launch in Safari, it is replacing the '#' with '%23', which does not load. If the link is pasted, it works as expected and it has continued to work in Android.

    I know that Targit does not troubleshoot iOS or 3rd party apps, but this seems like a big issue when dealing with these '#'s in URLs. Is Targit working on a newer way to use embedded links or have any suggestions for us?

    Thanks

    2

Please sign in to leave a comment.

Didn't find what you were looking for?

New post