You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are migrating our quicksight datasets and analyses from our staging account to our prod one via a node script. The analysis and datasets have been created on the Quicksight UI and we're using a nodejs script to create and update the datasets/analyses in the prod account.
Some analyses custom unicode glyphicon icons have been added in the TableVisual without error and work/display correctly on the analysis and associated dashboard. However, when we fetch the analysis data from the staging account in the node script and try and create the analysis in the prod account using the CreateAnalysisCommand it throws an error.
The error comes from the regex for the ConditionalFormattingCustomIconOptions but I'm not sure if this has been limited to only a certain range of BMP glyph icon string values on purpose, or if it is an oversight.
One analysis includes some custom glyph icons which are SMP (emoji) glyph icons.
Wondering if there is a workaround for this? At the moment we're removing the unicode glyphicons in the script and then re-adding them manually in the QS UI on the prod account, but I just don't understand why this is necessary. There are other emoji icons used elsewhere on the same analysis which migrate fine in the script, it just seems to be these specific custom unicode glyphs which are the issue within the TableVisual object of the Sheets array.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are migrating our quicksight datasets and analyses from our staging account to our prod one via a node script. The analysis and datasets have been created on the Quicksight UI and we're using a nodejs script to create and update the datasets/analyses in the prod account.
Some analyses custom unicode glyphicon icons have been added in the TableVisual without error and work/display correctly on the analysis and associated dashboard. However, when we fetch the analysis data from the staging account in the node script and try and create the analysis in the prod account using the
CreateAnalysisCommand
it throws an error.The error comes from the regex for the ConditionalFormattingCustomIconOptions but I'm not sure if this has been limited to only a certain range of BMP glyph icon string values on purpose, or if it is an oversight.
One analysis includes some custom glyph icons which are SMP (emoji) glyph icons.
Wondering if there is a workaround for this? At the moment we're removing the unicode glyphicons in the script and then re-adding them manually in the QS UI on the prod account, but I just don't understand why this is necessary. There are other emoji icons used elsewhere on the same analysis which migrate fine in the script, it just seems to be these specific custom unicode glyphs which are the issue within the
TableVisual
object of theSheets
array.Beta Was this translation helpful? Give feedback.
All reactions