Selecting multi-word fields
When trying to troubleshoot a loop node I noticed this. I want to pull a specific URL field from an item, and the field has a 2-word name. I tried using item["Directions Link"], (probably the wrong thing to do?) but every time I do that the editor automatically removes the structure and reverses the input, or just declares it invalid...
Theres definitely a bug in there causing the reversal, but also how should I be selecting what I would normally write as object["field name"]?
2 Replies
AI Support Bot Information
<@791353343426953246> 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
The issue you're encountering seems to be related to how you're trying to access a field with a space in its name in the BuildShip workflow editor. The reversal or invalid declaration might be due to the editor not properly recognizing the structure you are using.
In BuildShip, when dealing with field names that contain spaces or special characters, it's generally a good practice to replace spaces with underscores or similar characters in the UI, if possible. If you must keep the space in the field name, ensure that the access syntax is correct and supported by the BuildShip editor.
Here's a correct approach to accessing a field with spaces in a JSON object within BuildShip:
1. Use Bracket Notation: Ensure you're using the bracket notation correctly. It allows you to use strings as the field name. For example,
item["Directions Link"] is a valid way to access the field.
2. Ensuring Compatibility: Double-check BuildShip documentation or consult support to ensure that accessing fields with spaces in their names is supported and if there are specific configurations or restrictions involved in your specific case.
3. Debugging: Try using a different method or simplifying your setup to see if the issue persists. You can perhaps rename the fields to a single word without spaces and test if the error still occurs.
If you're still experiencing an issue, it could be beneficial to report this as a potential bug to the BuildShip support team with details, including your exact setup and what reversals are occurring, as they might provide a specific solution or fix.
For more guidance about using the Loop Node, refer to the documentation:
Loop Node Documentation
If these suggestions do not resolve your issue, it may be helpful to reach out to BuildShip's in-app support for more tailored assistance.
BuildShip AI Support