Since the most recent release in Analytics, I am unable to share the embedded components of my pre-existing Workspace (segments and calculated metrics). I've both Curated Components and clicked on Share and checked the Embedded Components option in the Share Form. My end-users can see the Workspace, but are unable to access any of the segments or metrics within it. I've confirmed by going to the Segments inventory and "shared with" is empty. So I am having to manually share dozens of components with individual people. Is anyone else having this issue? Anyone know of a workaround?
Reopen the ticket, indicating the issue is not yet resolved.
In your response, provide them with the exact steps they need to take to reproduce the issue. This is down to the username to log in as, which buttons to click, which project to open, and which users to share with.
Once the agent can see it broken, they'll be able to do some experimentation to determine the scope of the issue, and figure out what is different between the project in question and a new project.
Once you're able to walk customer care through the bug, they'll either be able to provide a workaround and/or get engineering to fix it.
They're listed in the Segments components inventory. And even when I create a metric or segment within the workspace, they've always been created globally - meaning I can see them in my inventory, use them across the Adobe Analytics products, and share them individually and manually. It's only the shortcut that doesn't work to 'share all' associated with the specific Workspace.
Agreed with Urs here - this sounds like a regression bug. If you have an incident number I can check to make sure both parties have the information needed to get this fixed.
Maybe you can help... As a result of my ticket, I received the standard response - "it worked for me, so...". It appears that it happens with existing Workspaces and not anything built brand new. So any help you can offer in getting it resolved for existing workspaces would be helpful.
Reopen the ticket, indicating the issue is not yet resolved.
In your response, provide them with the exact steps they need to take to reproduce the issue. This is down to the username to log in as, which buttons to click, which project to open, and which users to share with.
Once the agent can see it broken, they'll be able to do some experimentation to determine the scope of the issue, and figure out what is different between the project in question and a new project.
Once you're able to walk customer care through the bug, they'll either be able to provide a workaround and/or get engineering to fix it.
