Notifications
Clear all
Features
2
Posts
2
Users
0
Reactions
4
Views
Topic starter
The concept:
Hello!
I have the following two requests:
Request 1
Resource: Record, Operation: Get & Search
To include an option for setting the key: “returnFieldsByFieldId” in the request.
Request 2
Resource: Record, Operation: Create or Update
When utilizing the Create or Update operation with “Map Automatically,” it would be beneficial to either allow the user to set the value for “Columns to Match On” (fieldsToMergeOn) in a text/expression field, and/or add a “Use Field IDs” option to permit passing field IDs instead of field names. Currently, if one selects “Field1” and “Field2” for columns to merge on, and the input data from the previous step has field IDs as keys instead of the field names, the request will fail (given the fieldsToMergeOn key is being set as the field names based on the select options).
My use case:
I have consistently used field IDs when building workflows because many individuals utilize our bases, and employing field IDs ensures that if someone modifies a field name, it does not disrupt any associated workflows. Consequently, in almost all scenarios, I resort to using the HTTP request node for Airtable interactions. I genuinely appreciate the Airtable node, as its use would significantly expedite my workflow creation process, but I am hesitant to rely on Field Names.
I think it would be beneficial to add this because:
For the majority of use cases, I believe using field IDs represents best practice, with the exception perhaps of situations where you intend for your workflow to function across multiple tables sharing identical column names (although even in this circumstance, there are straightforward methods to dynamically adjust field IDs within callin.io).
I'm uncertain about the prevalence of dedicated field ID users, but I am confident this feature would greatly simplify my workflow management and also benefit less technical users.
Any resources to support this?
N/A
Are you willing to work on this?
Yes, although I am not highly experienced and would require some guidance or direction to relevant resources.
Posted : 12/08/2023 1:35 am
I'm also very interested in a similar capability and would be willing to offer a bounty of $300 for it.
Specifically, I'd like to request an enhancement for the Airtable node in callin.io. Currently, the node requires field names when creating or updating records, but Airtable’s API utilizes field IDs. This can lead to issues, particularly when field names are altered or include special characters, causing workflows to break.
A comparable functionality for targeting tables by ID instead of table name has been discussed and implemented (refer to this thread), and having a similar feature for fields would be extremely beneficial. There was a similar feature request here, but it hasn't gained significant traction.
Proposed Solution:
- Incorporate an option for the Airtable node to accept field IDs rather than field names for record creation and updates.
- Within the callin.io UI, fields should continue to display their names for straightforward configuration, but the underlying logic should employ field IDs, thereby enhancing workflow resilience against Airtable schema modifications.
Functional Requirements
- The Airtable node must permit the use of field IDs for both "Create" and "Update" operations.
- The UI should present field names during configuration but utilize field IDs in API calls.
Compatibility & Documentation
- Confirm that the feature supports all Airtable data types and includes appropriate error handling.
- Update the documentation to detail the feature's usage and any toggle options for field name versus field ID.
Testing
- Furnish test cases demonstrating the feature's functionality with field name changes and special characters.
- Include a basic workflow test that showcases functionality for both single and batch records.
Review
- The feature is integrated into the main branch and operational.
Bounty: I am offering $300 for this, but I am open to negotiation based on complexity and feedback. If you are interested or require clarification, please get in touch.
Posted : 27/09/2024 4:59 pm