Conditional Formatting not working with Quicksight SDK getting Invalid Conditional Format error

Question & Answer
, ,
1

Hi Team,

I am getting below error when trying to create table visual with conditional formatting using Quicksight SDK. Used fields are part of sheet and visual.

[{Type: INVALID_CONDITIONAL_FORMATTING_EXPRESSION,Message: Error while parsing conditional formatting expression: {Base Facts.Units} > 2000. Error : Unsupported expression: {Base Facts.Units} > 2000, Errors: Didn’t find field Base Facts.Units,ViolatedEntities: [{Path: sheet/e0070b77-c321-4648-8543-30ce15ea8e84/visual/b7245506-1442-492c-90e6-6dd0049642df}]}

Please note, this field is present in dataset json as well as in analysis json, also when I have created visual manually on Quicksight with same configuration it is created but when I try to extract json for manaully created visual(using SDK) and compare it with mine it is exactly same, when I try to update the analysis name for extracted json and try to create it using SDK it is giving me same error.

Also, as the field used contains space I have tried rename field at dataset level even after that as well I am getting same error.

Can someone please help me on this

2

Hi @anshul1243,
Same as with your other question about Line Chart Visual:

Have you tried the LENIENT mode as the ValidationStrategy when using the CreateAnalysis API ? It is an option to relax the validation that is required to create and update analyses, dashboards, and templates with definition objects. When you set this value to LENIENT, validation is skipped for specific errors.

Did this answer your question? If so, please help the community out by marking this answer as “Solution!”. Thanks!

If it doesn’t solve your problem, I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. 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. Hope this helps!

1 Like