Genesyscloud_analytics_view 422 Unprocessable Entity on AU-1 BYOC

General Discussion
1

Quick question about analytics view provisioning failing during Terraform apply on our BYOC environment.

We are automating the setup of reporting resources using genesyscloud_analytics_view. The deployment works fine in our global test environment but consistently fails on the AU-1 BYOC instance with a 422 error.

Env: AU-1 BYOC
Provider: 2.5.1
TF: 1.6.0
Resource: genesyscloud_analytics_view

The HCL block is standard:

resource "genesyscloud_analytics_view" "csat_summary" {
 name = "CSAT Summary View"
 description = "Automated CSAT view"
 type = "query"
 query {
 dataset = "conversation"
 filters = [
 {
 name = "conversation.metrics.customer.satisfaction.score"
 op = "neq"
 value = "0"
 }
 ]
 }
}

Error output:

Error: error creating analytics view: 422 Unprocessable Entity
Response body: {“code”:“invalid_request_body”,“message”:“The request body was invalid”,“details”:[{“code”:“invalid_value”,“message”:“Invalid filter value for metric conversation.metrics.customer.satisfaction.score”}]}

The filter logic is valid according to the API documentation. We have verified the metric name exists in the BYOC instance via the REST API explorer. The issue seems specific to the BYOC environment or a version mismatch in the provider handling of BYOC specific metric schemas.

Has anyone encountered similar issues with analytics views on BYOC? Any workarounds or known fixes in newer provider versions? We are unable to proceed with our automated reporting dashboard deployment until this is resolved.

Any insights would be appreciated. We are considering switching to direct API calls via GitHub Actions if the Terraform provider cannot handle this correctly.