%20 instead of blank space in Alteryx Gallery.

Hi everyone,

I updated an Alteryx Server (Test Server) with embedded MongoDB and every component installed on a single machine, from 2021.2 to 2022.3. After the upgrade, I noticed that the blank spaces in the collection names were replaced by %20. Currently, everything is working as intended, but I wonder if this change could affect any scheduling, or anything else that maybe I am not aware of.

Has anyone else experienced this issue?

What impact could this change have on the correct functioning of the server?

What should I have in mind when I update the production server?

I'd appreciate any insights.

Thanks for the help.

Gallery

MongoDB

Upgrades

Updates

Accepted answers

fmvizcaino

Hey @nicolas_hernandez ,

I`ve seen this issue before when migrating workflows from one environment to another and it looks like a conversion error. I advise you to reach out to Alteryx support and make them aware of the issue so they can check and correct it if needed for the newer versions.

Luckily, you will be able to test first in your TEST server but I wouldn`t worry. Alteryx does everything through internal IDs so the names are merely for the front-end.

Best regards,

Fernando Vizcaino

All comments

fmvizcaino

Hey @nicolas_hernandez ,

Luckily, you will be able to test first in your TEST server but I wouldn`t worry. Alteryx does everything through internal IDs so the names are merely for the front-end.

Best regards,

Fernando Vizcaino

nicolas_hernandez

Hi Fernando,

Thank you for your prompt answer!

Knowing that Alteryx does everything through internal IDs gives me better insight of any possible impact. Also, it seems this issue was already addressed in 2021.4 (Defect TCPE-473), I wonder if this is a recurring issue or if it happened because of the leap between versions during the upgrade.

Anyway, thank you again for your answer.

Best regards,

Nicolas

fmvizcaino

You are absolutely right. The names were URLencoded until 21.4 and since you migrated from 21.2, the issue still remained there. The good thing is that you can manually rename according to the instructions from that defect.

Best,

Fernando Vizcaino

yuriy

I figured it out for my case. The issue was due to the difference between the server and designer. We built a new server env with version 2024.2, while Designer was still on 2023.1. To resolve this, I upgraded designer to the same version, removed server URL, added it again. Now it shows with spaces

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15867

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703