I’m trying to use Asset Bundle export and Import API to export the dashboard with same account. I tried different ways by changing dataset, provide new dashboard id and Name only. simplest way I tried to use override parameter with ResourceIdOverrideConfiguration just add prefix in resource. to use this I have successfully exported the dashboard without dependencies and Importe it. I am unable to find the dashbord with prefix even describe-asset-bundle-import-job is successful. Am I missing something?
Hi @Hitesh - Welcome to AWS Quicksight and thanks for posting the question. Looking at your describe command, can you please put the condition as Test_ as all your resources are created with _ not -. Please check this once.
Hi Hitesh - I am thinking of permission issue to your newly created dashboard. Is it possible to update the permission and check once. To update the permission, please use the api - update dashboard permission.
Hi Sanjeet, To run this permission API I need dashboard id, and we don’t have the new dashboard id created by Import API. that is the issue once we have new ARN from Api. we can provide permissions.
Hi @Hitesh - Good point. Is it possible to list all dashboards to a notepad and see what are the dashboards are available in your account. The bundle import job was successful with 200 message which ensure all artifacts are imported correctly. Also it is possible to login to QuickSight console and check whether dashboard is available or not.
If nothing is working, i will suggest submit a ticket to AWS so that they can analyze the issue by screen share and check the backend logs.
Hi @Sanjeeb2022, I try each and everything, even download the whole list as Json in notepad. check quick sight console but not able to find. I think you are right I need to open ticket with Aws and share cloud trail with them to check.
Thanks, Sanjeeb.
Hi @Hitesh - Thanks. This is a strange and interesting issue. Once the issue will get resolve, please share the root cause and solution to the whole community for the knowledge share.
Not sure if you have tried using the same dashboard id.
The dashboard id would be same post import as the dashboard id referred in export. Also from the console, if you have admin role you can go to manage assets to search the asset by name and share it with required users.
Also as @Sanjeeb2022 mentioned , you can try granting access to the dashboard through API using the same dashboard id.
Hi @prantika_sinha, Thanks for reply. End goal of export and import asset bundle I think you will be able to export your dashboard/ analysis to another aws account or within same account where you have different data source or data set may be because of data isolation. In that case admin share access will not work. If dashboard id will be the same than that dashboard id already have permissions. and we have orverride parameter from aws to override the dataset, datasource and even dashboard name and id(AssetBundleImportJobDashboardOverrideParameters - Amazon QuickSight)
@Sanjeeb2022 I am able to find the resource with Test Prefix only in front of dashboard id. Name is not got updated. I need to check with AWS because that override parameter is not working mention in documents because I just tired some other parameters also. its same job is successful, and nothing get reflected. I will keep you updated.
As per my knowledge, permissions are not carried forward while importing dashboards. QS assets are specific to region and accounts and similarly asset ids are unique at account-region level. So permission vary every time we import it as a new asset. However you can override permission while importing. AssetBundleImportJobDashboardOverridePermissions - Amazon QuickSight.
@prantika_sinha Correct but when we override the dataset or my dashboard ID according to documentation than new Resouces will get created with the ID you given and ideally you can provide the permission to the resource which exist. In my case when I override dashboard ID nothing in aws with new resource id/ dashboard id. So I cannot give permission.
Hi @Hitesh,
It’s been awhile since the last communication in this thread; were you able to find a work around for your case or did you have any additional questions?
If we do not hear back within the next 3 business days, I’ll go ahead and close out this topic.
Hi @Hitesh,
Since we haven’t heard back, I’ll go ahead and close out this topic. However, if you have any additional questions, feel free to create a new topic in the community and link this discussion if it contains relevant information that may be needed.
