In one of my production workflows expressions does not work
"Dot Field" notation should extract field value form object - but in one of my workflows it does not. please help!
Solution:Jump to solution
Hey @dbrwk, could you please clear the expression, try switching to "JavaScript" using the dropdown at the bottom of the expression editor (where it currently says "Text"), and add the expression you want again and test it to see if it works?
4 Replies
AI Support Bot Information
<@331061842753355788> you can react on the relevant answer (message) with a ✅ in this thread when you think it has been solved, by the bot or by a human!
Anyone can react on this message with a ❌ if the GPT bot is unhelpful or hallucinating answers.
Please note: Team members will review and answer the questions on best efforts basis.
AI Response
To use dot notation to extract a value from a field within a JSON object in BuildShip workflows, it is done within the expression editor. It seems that you already know this but it's not working in your particular workflow. Here's a step that you might find helpful:
1. Correct Field Path: Double-check that the path to the field in your JSON object is correct. Ensure you are using the exact hierarchy of the keys.
2. Expression Editor: Make sure you are using the expression editor correctly within the node where you are attempting to access the field value. Example syntax in the expression editor would be
object.field.
If you're encountering issues, it might be worth revisiting a specific example or template that correctly makes use of dot notation. You can see how it’s done in a workflow example with Supabase by exploring this link for reference: Supabase Create Row Node Example【4:0†buildship-support-site.json】.
If you continue facing challenges with it despite following these steps, consider reaching out through BuildShip's support for a more tailored walkthrough【4:18†buildship-docs.json】.
BuildShip AI Support
Solution
Hey @dbrwk, could you please clear the expression, try switching to "JavaScript" using the dropdown at the bottom of the expression editor (where it currently says "Text"), and add the expression you want again and test it to see if it works?
@nithinrdy that seems to work, thanks.