Repository navigation
Flow API - action.core.getCatalogVariables warns catalog variable will be skipped when referencing variables outside scope [v4.13.3]
#139
Replies: 2 comments
|
The warning means the SDK did not resolve that variable for the action. In 4.13.3, I extracted and ran the 4.13.3 variable resolver from the published If your intent is to retrieve all variables on the template item, remove the The SDK 4.13.3 Flow Actions guide explicitly documents this as the way to copy all template variables, including those you have not enumerated in the action. It also warns that existing values on the requested item may be overwritten. If you need a subset, the variable set must be represented and attached in the Fluent catalog-item model so the resolver can find its variable names; supplying raw sys IDs does not bypass that lookup. |
|
Hi @BH0LL , @Arthur031221 Thanks for reporting this, and for the detailed analysis. We've confirmed this is a bug, and we're working on a fix. We'll update this thread once it's available. |
Uh oh!
There was an error while loading. Please reload this page.
Currently running version 4.13.3
I ran into this warning log a couple versions ago (I think 4.11.2), but can't remember exactly when it started. I wasn't totally sure if this meant that a reference to the variable was going to fail later in the flow as I was converting a pre-existing flow to the Flow API.
I'm seeking for some clarification on how to resolve this error and not drop catalog variables from the flow.
Steps to Reproduce
action.core.getCatalogVariables] that grabs a variable from the variable setnpm run buildAND/ORnpm run transform[now-sdk] WARN: Catalog variable '<sys_id>:item_option_new' not found in catalog item. It will be skipped.Older example of action:
New example of action:
All reactions