Member must have length greater than or equal to 1

Hi ALL,

I am getting one weird issue in Quicksight, when i am creating some text based visualization using insight visualization.

I am not getting any while creating a visualization in source account but when i am migrating the dashboard from source to target account.

I am getting below errors.

Value at ‘definition.sheets.3.member.visuals.12.member.insightVisual.insightConfiguration.computations.3.member.totalAggregation.value.numericalMeasureField.formatConfiguration.formatConfiguration.percentageDisplayFormatConfiguration.prefix’ failed to satisfy constraint: Member must have length greater than or equal to 1"

I know this issue is happening because of formatting properties.
under the unit section we have prefix and suffix but i am not providing any value to it so it is necessary to provide a value for it???

Hello @achourey hope this message finds you well

If I understand well your problem, gott some suggestions related to the formatting configuration for a numerical measure field in an insight visualisation. The error message indicates that the prefix field must have a length greater than or equal to 1, meaning it cannot be empty. To address this issue, you might consider the following approaches:

  1. Add a Blank Prefix: If the prefix field is not necessary for your visualisation, you could try adding a blank space as a prefix. This might satisfy the length constraint without altering the appearance of the visualisation.

  2. Set a Default Prefix: If a prefix is meaningful in the context of your visualisation, you could define a default value that is appropriate for the data being displayed.

  3. Check Migration Settings: Ensure that the formatting settings are being correctly migrated from the source environment to the target environment. Sometimes, settings can be lost or altered during the migration process.

  4. Update the Dashboard in the Target Environment: After migration, edit the dashboard in the target environment and verify that all formatting settings are correct. Adjust them as necessary.

Please, tell me if some of this suggestions works for u :smiley:

Hello Lary,

Even I’m getting same issue while migration & I tried adding blank prefix to the visual (although it is out of my business requirement) but it’s still failing. Migration setting/ migration script is fine because it is not failing for every report, only few of them are failing

Please let me know if you find solution for this.