EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB483196: In Web, when the entity reference &current is used in a dossier HTML container URL, it is encoded into a symbol (¤)


Community Admin

• Strategy


In Web 2019, when the entity reference &current is used in a dossier HTML container URL, then it is encoded into ¤. This kb article provides a workaround for this issue.

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
In a dossier where the entity reference

¤
 is used in a URL in an HTML container, the Strategy Environment converts this into an unknown entity (symbol). This occurs because
&
is considered the beginning of an entity reference.

Steps to Reproduce


1. In Web, open a dossier.
2. Click the HTML Container icon.

ka0PW0000001JjBYAU_0EM2R000000gvRg.jpeg

3. In the HTML container, click HTML Text.

ka0PW0000001JjBYAU_0EM2R000000gvRv.jpeg

4. Paste the following HTML code in the container and click OK.

<html> <body> <a href="./mstrWeb? evt=2048001&src=mstrWeb.2048001¤tViewMedia=2"><img id="site-logo" src="https://www.Strategy.com/getmedia/3534c22d-a593-4ecc-bbec-c8c6ac3deab5/logo" alt="Strategy"></a> </body> </html>

5. Click on the image and see
¤tViewMedia
is converted into
¤tViewMedia
.

ka0PW0000001JjBYAU_0EM2R000000gvu9.jpeg

Cause


The reason the symbol appears is because

&
is considered to be the start of an entity, in this situation,
¤
 is decoded as the
¤
symbol. In other situations, using
&
results in the correct conversion. For example, 
©
is ©. However, that is not the case in this instance.

Workaround

This issue was reviewed by our technology team for feasibility and will not be scoped for a code fix in any upcoming release. As such, for a workaround, you can encode 

¤tViewMedia
with
&currentViewMedia
or put
currentViewMedia
as the first parameter in the URL API.
 
KB483196


Comment

0 comments

Details

Knowledge Article

Published:

April 25, 2019

Last Updated:

March 21, 2024