ENCODEURL() on key columns

[Julien]

Hi Community,

I have noticed that sometimes an image does not display in a pdf (or html) report even if that image displays in the App.

The reason I have identified is that there were some special characters (such as "é" ; "è" ; "°" ; etc.) inside the key column of the same table. The image is named after the key column and its own column name.

So I'm about to use the ENCODEURL() on each of my key columns of tables where an image is present.

I wanted to know if you have counter indication regarding this?

Would you say it's a good practice ?

Or is there a bad effect that I didn't think of ?

Thanks guys! 

[Aurelien]

Hi @Julien 

I would suggest using the dedicated key_columns expression UNIQUEID() in the Initial value field, that has no special character in it.

Then use an expression to get the pdf/file paths where you need it.

For reference:

UNIQUEID() 

Data: The Essentials 

[Julien]

Thanks Aurelien, I use also UNIQUEID() it is usually something like: [Name]&"_"&UNIQUEID() so as to keep to automate the naming of the picture when saved on the drive.  My question is : is ENCODEURL([Name]&"_"&UNIQUEID()) a better solution ? It seems Steve agrees 🙂

[Steve]

Using ENCODEURL() here is best-practice.

[Aurelien]

I agree as well. 

From @Steve or me, you should always prefer Steve's wisdom 😜

[SkrOYC]

🤣

lol