Conditional formatting getting lost on bundle import

Question & Answer
, , ,
1

We have a bundle promotion process that uses the StartAssetBundleExportJob and StartAssetBundleImportJob to promote analysis changes up to our production environment.

We are using conditional formatting in some of our analysis, but we noticed that during the promotion process these configurations are getting lost. We can see the conditionalFormatting blocks are present in the exported bundle. There are no errors during the import process - the target analysis simply does not have any conditional formatting defined.

We can also see from an export and comparison of the analysis json in both the source and target environments post-promotion that the conditionalFormatting blocks are completely missing in the target analysis.

image
image2740Ă—967 295 KB

This seems to be some kind of bug. Any suggestions or workarounds would be appreciated.

2

@cashcraft ,

I have run a test at my end and was not able to replicate any loss in conditional formatting .

I would recommend to create AWS support ticket so that our support engineers will be able to check the logs assist further on this.

Here are the steps for opening a support ticket - Creating support cases and case management - AWS Support . If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf

Kind regards,
Koushik

3

Thanks @Koushik_Muthanna . One other detail I should add - this seems to only be happening when we import to a different quicksight account. When importing back into the same account we don’t see the issue.

4

Hi @cashcraft,
It’s been awhile since last communication on this thread, were you able to successfully file a support ticket and receive additional help on this case or did you have any additional questions?

If we do not hear back within the next 3 business days, I’ll close out this topic.

Thank you!

5

Hi @cashcraft,
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 post in the community.

Thank you

1 Like
6

Just to wrap this… AWS has identified the issue and is working on a permenant fix. In the meantime, they have provided the following response with a workaround…

AWS Support Response:

Based on my discussions with the engineering team, they have been working on to address the issue in the long term. However, they have proposed a workaround that should help you avoid issues with conditional formatting while performing export and import of assets via Asset Bundle API. Please find the steps below>
I have also been able to test this workaround and it appears to be working fine.

— Steps

  1. In the source analysis, open the Parameters pane
  2. Filter the DataSet Parameters section using the UNMAPPED filter
  3. For each parameter:
    Select the parameter
    Click Mapped Parameter > Create new
    Create a new mapping with the same parameter name
  4. Repeat until all parameters are mapped

Post this mapping, you can perform an export import of the asset using the Asset Bundle API and we should be able to see the conditional formatting reflected in the target.
Unfortunately, at the time of writing this correspondence, I do not have an estimated time by when the long term fix would be available. At the time of writing this correspondence,it is currently being worked upon.