Hey folks, I am having a troubles with creating a ...
# gooddata-cloud
j
Hey folks, I am having a troubles with creating a string parameters. When I try to do so, it throws Error: Only NUMBER parameters are supported instantly. Am I doing something wrong ?
k
The issue is likely that string parameters are gated behind a feature flag that needs to be enabled first. According to the SDK, there is an
enableStringParameters
feature flag that controls authoring of string (textual) what-if parameters. [Feature Flags] String parameter support was also introduced as an experimental feature in late July 2026. [What's New] Here's what to check: 1. Ensure the
enableStringParameters
feature flag is enabled
in your workspace/organization settings. Without it, only
NUMBER
parameters are supported in the catalog YAML editor, which would explain the error you're seeing. 2. Verify your YAML definition is correct. A valid string parameter definition looks like this🆔 scenario title: Scenario description: Controls which planning scenario is used in scenario-based metrics. definition: type: STRING defaultValue: Actual constraints: allowedValues: - Actual - Budget - Forecast tags: - Favorites[Create Parameters] 3. Check your GoodData version — string parameters require React SDK 11.49+ and Python SDK 1.71+. [What's New] If the feature flag is not yet enabled in your environment, you'll need to contact GoodData support or your administrator to have it turned on, as it is currently an experimental feature. 👍 0 button 👎 0 button â„šī¸ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.
j
While using your own example on the docs, I am getting this error now: - Favorites
Invalid constraints: STRING parameters allow non-negative integer minLength and maxLength, or allowedValues.
While using your own example on the docs, I am getting this error now: Invalid constraints: STRING parameters allow non-negative integer minLength and maxLength, or allowedValues.
j
Hi Jakub, looks like the remaining issue might be our documentation, not anything you did. The example on that page lists
allowedValues
as plain strings, but the editor expects each entry to be an object with a
value
key. This form should validate. Can you give it a try:
Copy code
id: scenario
title: Scenario
description: Controls which planning scenario is used in scenario-based metrics.
definition:
  type: STRING
  defaultValue: Actual
  constraints:
    allowedValues:
      - value: Actual
      - value: Budget
      - value: Forecast
tags:
  - Favorites