Hello,
I get strange behavior creating topic using “create-topic” cli command. I add parameter --topic-id, and run describe to validate creation and that gives me expected result.
Issue is that I see completely different id in Quicksight UI.
When I replace UI id with the one I set, topic can load normally in UI.
We use specific ids with prefixes so we know what topic, dashboard, dataset, etc. belong to what environment in case they’re on the same account.
Why does this happen with topics?
Hi @Natasa_Dj,
Just to make sure I understand this, I have a few questions to confirm. Are you looking at the same account and Region in both the CLI and the UI? When you open the topic in the browser, does the ID in the URL match the CLI ID or the unexpected one? And just to clarify, you’re receiving two different IDs but you’re able to see the same asset?
Hi @WLS-Cesar
Yes, I’m looking at the same account and region. When I open browser, topic id that is part of URL is not the one I set. I see the same asset with any of the 2 different ids.
The only issue is, that I don’t see the correct Id (the one I set) in the topic url. And this is important since I can have multiple environments in the same account with the same topic name.
When I set topic id using create-topic cli, I set it in a way that I can recognize which environment it belongs to.
In the meantime I’ve learned that this is a known issue, found similar thread. Old thread but it was assumed that this behavior is due to beta version. Q Topic ids appear different on UI and when queried through list-topics CLI command - #2 by WLS-DM
Hi @Natasa_Dj,
Thanks for answering those questions above. As for the post you mentioned, it appears it was marked as a feature request and unfortunately, I don’t believe there’s a workaround for the URL/id beyond what you’ve already discovered. I’ll mark this post as a feature request and archive it as well so that the AWS Product Team can have a greater chance of seeing this!