PipedreamHQ / PipedreamHQ/pipedream
[BUG] Configuration error in Crove's update document action when document id from previous step is used
- Dominant language
- JavaScript
- Stars
- 11.7k
- Forks
- 5.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 102
Description
**Describe the bug**
While configuring update document action of Crove's integration if we use the document id from the previous step of the workflow it shows some configuration error. In update document action dynamic fields are being populated with the help of entered document id, but when instead of manually adding the document id we use document id from the previous step no dynamic fields are populated and a configuration error is shown.
**To Reproduce**
Steps to reproduce the behavior:
1. Set up a new workflow and create a trigger from crove app e.g. document created trigger of crove app.
2. After testing the trigger create a new update document action of crove app.
3. While configuring update document action use document id from the previous step that is from document created trigger.
4. Instead of loading the dynamic fields it will a show a configuration error.
**Expected behavior**
When using the document id from previous step of workflow instead of showing configuration error it should load the dynamic fields.
**Screenshots**
Screenshots from the workflow

**Desktop**
- OS: Windows 11
- Browser: Chrome
- Version: 103.0.5060.66
Contributor guide
Assessment
This issue has not been assessed yet.