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

1 comment
  • 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

Please sign in to leave a comment.

Didn't find what you were looking for?

New post